Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
ivy-read in temporary buffer #717
It seems that if I call
Example. I am in a buffer where
After I choose a candidate, the message is
Is this intended, or if not is there a simple way to make sure the action is run in the buffer in which ivy-read was called?
Thanks, it works but actually I was just using
I'm not sure if this would raise some issues, but perhaps
could be replaced with
added a commit
Nov 29, 2016
The code I used to close this issue is not removed. It was causing too much trouble elsewhere.
This needs to be well-tested. I'll apply this change to my config to check if anything bad happens. If it doesn't, I'll apply this change.
Sorry about the trouble.
I also applied the change locally and tested a few things:
Of course there could be other issues I didn't come across. Please let me know if I can help with testing.
PS you surely noticed that the parentheses are not balanced in the code I posted above, it should be:
added a commit
Dec 4, 2016
I have actually found an undesirable (I think) effect of this
and choose eg
The solution that seems natural to me is to permanently switch to the buffer from which
I have tested that this works for the same four issues as above : #717 (current issue), #760 , #779 and #810 . But I'm not sure if this could create other issues (perhaps there are situations where one deliberately switches buffer during the candidate selection and wants the action to run in the new buffer?)
Incidentally, if I rewrite the above example using
then the same problem occurs but my proposed solution does not work. This is apparently because
I think it's fine: not perfect, but good enough.
The main reason why it's fine is that due to the possibility of
Sorry to bother you again, but I think the fix you applied in
And likewise in
But perhaps it makes sense to leave things as they are...