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

[End of buffer] issue #46

Closed
failable opened this issue May 16, 2020 · 6 comments
Closed

[End of buffer] issue #46

failable opened this issue May 16, 2020 · 6 comments

Comments

@failable
Copy link

I'm trying to get rid of ivy and swiper. When using ctrlf to find next search using, my muscle memory make me press C-n and I get

Screen Shot 2020-05-16 at 7 27 37 PM

Not a really big issue, and I may forget C-n and use C-s instead.

@raxod502
Copy link
Member

Is your intention with C-n to exit the search at the current candidate? If so, I don't think that's something I want to support, because the idea of CTRLF is that you don't accidentally exit the search by using any editing commands.

However, the duplicated [End of buffer] message is a bug. That does not occur for me with Emacs 28; I assume it is due to a difference in Emacs version. What are you on?

@failable
Copy link
Author

I mean the duplicates and I'm on GNU Emacs 27.0.91 (build 1, x86_64-apple-darwin19.4.0, Carbon Version 162 AppKit 1894.4). I'm also trying to avoid pressing C-n.

@raxod502
Copy link
Member

During the development since Emacs 26, a bug was introduced relating to minibuffer overlays, and it was subsequently fixed without making it into any release, although the bug stuck around for a while before being fixed. It's possible that you are experiencing this bug. Just to check, can you try it with the latest Emacs build and see if the same problem occurs?

If the bug doesn't occur in either the latest build or in any release, I am reluctant to complicate CTRLF further to work around it.

@failable
Copy link
Author

I build the latest emacs-mac

GNU Emacs 27.0.91 (build 1, x86_64-apple-darwin19.4.0, Carbon Version 162 AppKit 1894.4) of 2020-05-18

and the issue is still there.

@raxod502
Copy link
Member

raxod502 commented May 23, 2020

Thank you for the report. I reproduced the issue and believe I fixed it. Please let me know if the change works for you.

@raxod502
Copy link
Member

This thread is being closed automatically by Tidier because it is labeled with "waiting on response" and has not seen any activity for 90 days. But don't worry—if you have any information that might advance the discussion, leave a comment and I will be happy to reopen the thread :)

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

No branches or pull requests

2 participants