After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 699658 - Find : Ctrl+F then <Enter> key should "Find Next"
Find : Ctrl+F then <Enter> key should "Find Next"
Status: RESOLVED DUPLICATE of bug 650471
Product: gedit
Classification: Applications
Component: search and replace
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: Gedit maintainers
Gedit maintainers
Depends on:
Blocks:
 
 
Reported: 2013-05-04 05:16 UTC by John Smith
Modified: 2014-01-19 15:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description John Smith 2013-05-04 05:16:13 UTC 
A common workflow in many "text" applications (such as Firefox, Chrome, Eclipse, Geany) to find text is :
1. Select text
2. Ctrl+F to Find
3. <Enter> key to "Find Next"

In the GEdit Find dialog <Enter> key seems to only close the dialog.

<Enter> is commonly associated with "doing" the current action - in this case Find, or "Find Next", and not closing a dialog.

Noted that Arrow Up/Down and Ctrl+G can also be used to "Find Next".
Comment 1 Adam Dingle 2013-05-19 00:26:41 UTC 
I agree with this.  Similarly, Shift+Enter should find the previous match (as it does in Epiphany, for example).
Comment 2 Adam Dingle 2013-06-01 21:54:01 UTC 
We should also change the behavior of the Escape key when searching.  Today, searching in gedit works like this:

down arrow: move to next result
Enter: cancel search, keep current cursor position
Escape: cancel search, move cursor back to where it was when you began searching

Epiphany, Evince and other applications work like this:

Enter: move to next search result
Escape: cancel search, keep current cursor position

I think we should make gedit behave like these apps when the user presses either Enter or Escape.
Comment 3 Sébastien Wilmet 2014-01-19 15:16:46 UTC 

*** This bug has been marked as a duplicate of bug 650471 ***