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 305646 - Interactive search cannot descend to hidden file
Interactive search cannot descend to hidden file
Status: RESOLVED DUPLICATE of bug 136541
Product: gtk+
Classification: Platform
Component: Widget: GtkFileChooser
2.6.x
Other Linux
: Normal normal
: Small feature
Assigned To: gtk-bugs
Federico Mena Quintero
Depends on:
Blocks:
 
 
Reported: 2005-05-27 11:08 UTC by Russel Winder
Modified: 2006-04-13 02:26 UTC
See Also:
GNOME target: ---
GNOME version: 2.5/2.6



Description Russel Winder 2005-05-27 11:08:01 UTC
Distribution/Version: Debian GNU/Linux Testing

From Evolution 2.0.4 Composer trying to add an attachment brings up the File
Selector.  Focussing on the right hand side list box and typing brings up the
entry text box.  All this works fine.  If the typed string is a directory that
is listed then pressing return descends exactly as expected.  If the directory
exists but is not shown, i.e. it is a hidden file not shown then there is no
action.  If hidden files are shown then typing the name and pressing return
works.  This implies that you can only descend into shown files rather than
existing files which seems wrong.

Although I see the problem through Evolution use I am told this is a GTK issue
and that I should report this here.

I did a brief trawl through to see if this had already been reported but
couldn't see anything.  Apologies if it is a replica.
Comment 1 Matthias Clasen 2005-05-27 13:37:59 UTC
Hmm, we should fix that. As a workaround, you can open the context menu on the
file list and select "Show hidden".
Comment 2 Matthias Clasen 2005-05-27 16:08:43 UTC
This is somewhat hard to fix, since the typeahead search is a treeview feature
that just searches through a column in the tree model, it doesn't know anything
about hidden files.

One approach would be to recognize if the user types . or /. and then
temporarily make hidden files visible. 
Comment 3 Federico Mena Quintero 2005-05-31 15:05:43 UTC
Retitling for clarity.
Comment 4 gbz 2005-07-26 15:11:54 UTC
Typing "/" in the file selector triggers the CTRL+L dialog, which has
autocompletion including hidden files too. So shouldn't "." work the same as
"/", meaning it should pop up the CTRL+L dialog?
Comment 5 Matthias Clasen 2005-08-02 04:27:24 UTC
*** Bug 312265 has been marked as a duplicate of this bug. ***
Comment 6 gbz 2005-08-14 11:39:56 UTC
I suggest "~" too should work as described in #4, what do you think?
Comment 7 Yevgen Muntyan 2005-08-14 11:50:48 UTC
In the comment #2 Matthias says "This is somewhat hard to fix, since the
typeahead search is a treeview feature...". So why use this feature at all? Why
should GtkFileChooser use treeview search which has no idea about files?

Please take a look at svn://svn.berlios.de/ggap/junk/moofileview . Try to type
name of a file in the list or type '/tmp/', and note that this 'search' is not
like in GtkFileChooser, it's implemented in the file widget. (Please note, I am
not saying that is how FileChooser should look like).
Comment 8 gnutter 2006-02-24 23:06:02 UTC
Here's a screenshot of a modified filechooser in "save" mode. Snapped 
from Gimp, hence the image preview panel.

http://bugzilla.gnome.org/attachment.cgi?id=59500

Since the save version has the text input visible I would like to take
this as a model for file open as well.

It opens in this state with file browser open and the now redundant 
combo hidden.

This cleans the dialogue up and makes it much closer in appearance to
the file open dlg. 

I think both versions should be very similar in appearance, what ever
that ends up being.
Comment 9 gnutter 2006-02-24 23:07:00 UTC
sorry mistakenly posted to this bug.
Comment 10 Federico Mena Quintero 2006-04-13 02:26:45 UTC
Fixed as part of the federico-filename-entry branch.  This will get merged into HEAD soon.  Meanwhile, I'll mark this as a duplicate of the general "need a location entry" bug.

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