Bug 309608 - Allow "Next" in the search view to be executed (and bound) outside of the search view
Summary: Allow "Next" in the search view to be executed (and bound) outside of the sea...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 3.5   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 115202
Blocks:
  Show dependency tree
 
Reported: 2010-04-18 16:46 EDT by David M. Karr CLA
Modified: 2019-09-06 15:37 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David M. Karr CLA 2010-04-18 16:46:04 EDT
Build Identifier: M20100211-1343

I prefer to use the keyboard as much as possible, and as efficiently as possible (I'm not handicapped, I just consider the mouse a handicap :) ).  That's why it's annoying when a series of steps I have to go through can't be done easily from the keyboard.

I'm often in a situation where my focus is in the editor view, and the search view is visible, and I want to go to the next occurrence from the search view. Right now, I have to go to the search view and execute the "Next" command, which goes to the next search occurrence.

There is already a key bound to put the focus in the search view, so I could press that key, and then Ctrl+. to go to the next occurrence.  That works, but it would be better if the "Next" command in the search view could be globally bound, so I could press a key in the editor view which would bring me to the next search occurrence.

On a side point, I use the Emacs+ plugin, which now has the ability to record keyboard macros.  I technically could record a macro consisting of the two key sequences, the first to put the focus in the search view, and the second to go to the next occurrence.  Unfortunately, because of some oddity to how the "Show View" command works in Eclipse, when I execute "Show View (View: Search)" from within an Emacs+ keyboard macro, it just brings up the "Show View" dialog, allowing me to select the view I want (which doesn't work in a macro).  The key I have bound to "Show View (View: Search)" works perfectly fine when not inside an Emacs+ keyboard macro.  I've sent a comment about this last point to the Emacs+ maintainer.

Reproducible: Always
Comment 1 Dani Megert CLA 2010-04-19 04:34:57 EDT
You can use Ctrl+. and Ctrl+, to step through the editor annotations. Which annotations are caught can be configured in the Next/Previous Annotation toolbar drop down.
Comment 2 David M. Karr CLA 2010-04-19 10:01:24 EDT
I'm confused. I suggest you read the original description again.  This has nothing to do with stepping through editor annotations. I'm trying to step through the search locations found in the search view, but I'm trying to do that from the editor view. That's why this is an enhancement request.
Comment 3 Dani Megert CLA 2010-04-19 10:24:43 EDT
Got it: you also want to switch to the next editor globally, similar to bug 115202.
Comment 4 David M. Karr CLA 2010-04-19 11:02:12 EDT
Exactly.  I'd go so far as to say that this bug I entered is a duplicate of that.  It's sad to see that this functionality has been wanted for 5 years now.
Comment 5 Paul Webster CLA 2010-11-16 08:56:39 EST
See experiment in bug 328460

PW
Comment 6 David M. Karr CLA 2010-11-16 12:04:12 EST
I now have this functionality by utilizing a saved keyboard macro with the Emacs+ plugin.

I described this implementation at <http://davidmichaelkarr.blogspot.com/2010/10/keyboard-nirvana-with-eclipse-and-emacs.html>.
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:37:32 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.