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 779711 - .hidden file: RFE to handle patterns and documentation
.hidden file: RFE to handle patterns and documentation
Product: glib
Classification: Platform
Component: gio
Other Linux
: Normal normal
: ---
Assigned To: gtkdev
Depends on:
Reported: 2017-03-07 16:31 UTC by garrett.mitchener
Modified: 2018-05-24 19:24 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description garrett.mitchener 2017-03-07 16:31:54 UTC
GIO has a feature where it looks for .hidden files and skips files listed therein.

- As best I can tell, it's not documented. I had to read through several undocumented functions to figure out how this feature works.

- I was looking for a solution to the following problem. Mercurial creates a lot of temporary files named hg-checkexec-* where the * part is a random sequence of characters. Icons for these files appear in nautilus and stick around long after the temporary files have been deleted. I have to manually refresh the view to get rid of them. I was hoping to find a way to tell nautilus to ignore them, and I stumbled across this gio feature. However, it won't solve my problem unless the .hidden file can include some kind of pattern matching (glob or regex). That would involve switching the implementation from a hash table to some other data structure.

(I don't know for sure, but I think mercurial creates all these files because it's cross platform and there may be features of file systems that can only be detected this way.)
Comment 1 GNOME Infrastructure Team 2018-05-24 19:24:54 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: