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.

Sign up for GitHub

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

Jump to bottom

ivy-done from counsel-yank-pop during counsel-ag, from a read-only buffer: "ivy-call: Buffer is read-only" #937

Closed
braham-snyder opened this issue Mar 26, 2017 · 3 comments
Closed

ivy-done from counsel-yank-pop during counsel-ag, from a read-only buffer: "ivy-call: Buffer is read-only" #937

braham-snyder opened this issue Mar 26, 2017 · 3 comments

Comments

@braham-snyder
Copy link
Contributor

showed up within the last week or so, perhaps related to the fixes to #924
@abo-abo
Copy link
Owner

abo-abo commented Mar 27, 2017

Thanks for the report. This is indeed a big issue. It's hard to figure out how to juggle this recursive state properly, especially since debugging minibuffer windows is awkward. I'll try to fix this today, possibly by reverting #924.

@abo-abo
Copy link
Owner

abo-abo commented Mar 27, 2017

Please test.

@braham-snyder
Copy link
Contributor Author

👌

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@abo-abo @braham-snyder