This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 250094 - Emacs keymap: repeatedly pressing Ctrl+S does not iterate through search results
Summary: Emacs keymap: repeatedly pressing Ctrl+S does not iterate through search results
Status: NEW
Alias: None
Product: editor
Classification: Unclassified
Component: Search (show other bugs)
Version: 8.1
Hardware: PC All
: P3 normal (vote)
Assignee: Milutin Kristofic
Depends on:
Reported: 2015-01-29 13:55 UTC by Roman Svitanic
Modified: 2015-02-03 10:22 UTC (History)
2 users (show)

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description Roman Svitanic 2015-01-29 13:55:35 UTC
I am just creating an issue for the bug report/request that came on Easel mailing list.

I'm attaching the quote from user's mail:
"After typing Ctrl-s in the editor you should be able to type what you are searching for and find it.  Then, subsequent Ctrl-s should let you do the incremental search.  Compare this emacs behavior to what NB does when using emacs short-cuts.  The default emacs short-cut bindings in NB certainly do not follow this, and I have not been able to manually set short-cuts to make it follow this pattern.  In NB, if you type ctrl-s it does nothing."

Please reassign this issue to the correct category if I have placed it wrongly.
Comment 1 fmorshed 2015-01-29 15:09:59 UTC
I recommend that you first familiarize yourself with emacs' ctrl-s behavior.  Just bring up emacs, type ctrl-s, give it a search string, type ctrl-s again, and again, and again.

Now, notice what happens when you click in the editor!

It is a simple behavior, but it has to be mimicked EXACTLY.

Thank you.

Comment 2 Milutin Kristofic 2015-02-03 10:22:24 UTC
You can use find next occurence (F3 in netbeans, alt+s in emacs)  for similar behavior. F3 searches what was last in searchbar, if nothing it will open searchbar. 

For behavior as you request, this must be implemented in search code.