Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323749 - [KeyBindings] Cmd+. does not 'find next' in 3.6 Cocoa
Summary: [KeyBindings] Cmd+. does not 'find next' in 3.6 Cocoa
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: PC Mac OS X - Carbon (unsup.)
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-26 15:24 EDT by Boris Bokowski CLA
Modified: 2021-10-04 14:26 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Boris Bokowski CLA 2010-08-26 15:24:39 EDT 
1. Do a search for references, for example: callers of WorkbenchActivityHelper.filterItem
2. In the Search view, the first match should be selected
3. Press Shift+Cmd+. for 'previous match' (this is Ctrl+, on Windows and Linux): works fine
4. Press Cmd+. for 'next match' (Ctrl+. on Windows and Linux): doesn't do anything.

The key binding does show up in the Keys preference page.
Comment 1 Eclipse Webmaster CLA 2019-09-06 16:19:17 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.
Comment 2 Eclipse Genie CLA 2021-10-04 14:26:19 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.

--
The automated Eclipse Genie.