Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In *helm-ag-edit* buffer, press c-c c-k will issue error message #1856

Closed
zilongshanren opened this issue Jun 5, 2015 · 9 comments
Closed

Comments

@zilongshanren
Copy link
Contributor

ad-Advice-select-window: Wrong type argument: window-live-p, #<window 369>

And the helm-ag-edit buffer can't be closed.

@tuhdo
Copy link
Contributor

tuhdo commented Jun 5, 2015

You should report to helm-ag and include a reproducible recipe.

@zilongshanren
Copy link
Contributor Author

@tuhdo I have installed helm-ag in a brand new Emacs config and it's ok.

@zilongshanren
Copy link
Contributor Author

@tuhdo I'm using the latest develop branch of spacemacs. Do you have this issue on your side?

@zilongshanren
Copy link
Contributor Author

@tuhdo

`
ad-Advice-select-window is a compiled Lisp function.

(ad-Advice-select-window AD--ADDOIT-FUNCTION WINDOW &optional NORECORD)

After-advice `powerline-select-window':
makes powerline aware of window changes

After-advice evil'.

I think this issue could only reproduce in spacemacs..

@syl20bnr
Copy link
Owner

syl20bnr commented Jun 5, 2015

@AndyQue did you find a work-around to close the buffer ? I think I encountered this bug once and it was ver yannoying because afterwards I was not able to use the editing feature of helm-ag anymore (had to restart emacs).

@zilongshanren
Copy link
Contributor Author

@syl20bnr Very strange behavior, I can't reproduce it now... If I can reproduce it in the future, I will try to find a work-around to this issue.

@zilongshanren
Copy link
Contributor Author

@syl20bnr BTW, I have upgraded all of my packages to the latest MELPA version. I'm not sure whether the issue is gone or not.

@StreakyCobra
Copy link
Contributor

As nobody reported this issue last 5 months, I assume it has been solved. I'm closing it, but feel free to open a new one in case of troubles ☺️

@zilongshanren
Copy link
Contributor Author

@StreakyCobra thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants