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 318324 - cycle through files when pressing a letter
cycle through files when pressing a letter
Status: RESOLVED OBSOLETE
Product: nautilus
Classification: Core
Component: File and Folder Operations
2.12.x
Other All
: Normal major
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 612675 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-10-09 08:51 UTC by Marius Andreiana
Modified: 2012-08-16 02:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Marius Andreiana 2005-10-09 08:51:17 UTC
Pressing letter "a" makes nautilus go to the first file in the list with that
letter. Pressing again "a" should make it go to the next (cycle).
Comment 1 Christian Neumair 2005-11-11 08:36:02 UTC
Thanks for your bug report!
With the current implementation (HEAD), you'll have to press
ctrl-g/ctrl-shift-g, or ctrl-up/down to browse results after pressing "a". Are
you ok with that?
Comment 2 Christian Neumair 2005-11-11 08:36:43 UTC
The keybindings are actually ctrl-g/ctrl-shift-g, resp. up/down.
Comment 3 Marius Andreiana 2005-11-11 13:05:25 UTC
The hordes of people migrating from Windows to Linux won't know that :)
Would be best to make it work like in the initial request (how Windows explorer
works). 
Also
* the file names should be considered case insensitive in this case by Nautilus. 
* folders and files shouldn't be different in this selection
(nautilus already works this way, please don't change)

Please take into account that list of names folders/files depends to current
sort (could be by size too, not only by filename) and view (list, icon...)

Perhaps this should be implemented in GTK's tree object, not in Nautilus?
Comment 4 Christian Neumair 2005-11-11 13:44:54 UTC
> The hordes of people migrating from Windows to Linux won't know that :)

Many of them probably use(d) Firefox [and hopefully switched to Epihany :)].

> the file names should be considered case insensitive in this case by Nautilus. 

I agree.
Comment 5 Christian Neumair 2005-11-11 13:46:50 UTC
> the file names should be considered case insensitive in this case by Nautilus. 

This is the case already, btw.
Comment 6 Nelson Benitez 2006-09-10 14:46:37 UTC
Besides what Christian says in comment 2 you can also use just UP or DOWN arrow key and mousewheel up/down to cycle next and previous match file. 

Although these keybindings are somewhat intuitive I wonder if adding a 'Next' and 'Previous' button next to the search entry would make this totally user friendly, especially if typeahead is expose to users through a menu item like the one I proposed on bug 328725 .
Comment 7 Marcus Carlson 2009-10-04 20:46:49 UTC
I can't remember how finding files in the folder was in late 2005 - did we have the little text entry at the corner? If not - is this bug still valid as you now see the text you enter (as in many other list in gnome)?
Comment 8 Allan Day 2010-06-21 11:51:56 UTC
*** Bug 612675 has been marked as a duplicate of this bug. ***
Comment 9 Allan Day 2010-06-21 11:54:42 UTC
The duplicate bug reports that this is a significant a11y issue. A number of other GNOME interfaces (including the panel) use the desired kind of behaviour for a11y reasons.
Comment 10 Stefano Teso 2011-02-09 13:31:27 UTC
This looks like a duplicate of Bug 317159
Comment 11 William Jon McCann 2012-08-16 02:19:51 UTC
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.