From: Josef Bacik <jbacik@redhat.com>
To: "Nicolò Chieffo" <84yelo3@gmail.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: interface to ask is a file is hidden
Date: Fri, 10 Oct 2008 15:21:04 -0400 [thread overview]
Message-ID: <20081010192104.GD19500@unused.rdu.redhat.com> (raw)
In-Reply-To: <641322f90810101222p3ff36ac3va9057b9958d2abf2@mail.gmail.com>
On Fri, Oct 10, 2008 at 09:22:11PM +0200, Nicolò Chieffo wrote:
> Recently there have been a discussion between the nautilus & GIO
> maintainer, and the ntfs-3g maintainer to implement a way to not show
> files in nautilus if they are hidden.
>
> Currently only files starting with a "." are hidden, as you can see in
> the GIO _g_local_file_info_get()
>
> if (basename != NULL && basename[0] == '.')
> g_file_info_set_is_hidden (info, TRUE);
>
> Of course, since we often have a multi-OS & multi-filesystem
> environment, it is a big limitation to consider hidden files only
> those files.
> There are some use cases in which we need a wider view of hidden files:
> - ntfs shared partitions & external disks
> - fat32 shared partitions & external disks
> - fat16 usb keys/multimedia devices
>
> Both the maintainers state that it's not a good idea to patch GIO to
> check which filesystem is hosting the file, and then ask it using the
> specific driver whether the file is hidden or not.
> Everything should be transparent for GIO, which should only make one
> call to a standard interface, that all filesystem drivers shall
> implement.
>
> Is it possible to consider this request?
> The discussion is in this moment hosted in the nautilus mailing list
> with this subject name: "nautilus & hidden files".
>
What files are determined as "hidden" is completely up to the application, and
not the filesystem. Every linux filesystem is going to return all entries in a
directory when you do a readdir, and then it is up to the app to cull which
entries it doesn't want. Having the fs/vfs arbitrarily decide which files are
"hidden" and shouldn't be returned via readdir is not the correct way to tackle
this problem, it should be decided via the application.
Josef
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-10-10 19:30 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-10 19:22 interface to ask is a file is hidden Nicolò Chieffo
2008-10-10 19:21 ` Josef Bacik [this message]
2008-10-10 19:35 ` Jeremy Allison
2008-10-10 20:00 ` Nicolò Chieffo
2008-10-10 19:57 ` Josef Bacik
2008-10-10 20:11 ` Nicolò Chieffo
2008-10-10 21:57 ` Theodore Tso
2008-10-10 22:01 ` Christoph Hellwig
2008-10-13 8:22 ` Alexander Larsson
2008-10-13 9:21 ` Nicolò Chieffo
2008-10-13 9:57 ` Christoph Hellwig
2008-10-13 10:37 ` Nicolò Chieffo
2008-10-13 10:37 ` Alexander Larsson
2008-10-13 10:43 ` Christoph Hellwig
2008-10-13 11:39 ` Alexander Larsson
2008-10-13 20:44 ` Jörn Engel
2008-10-13 20:50 ` Christoph Hellwig
2008-10-14 7:20 ` Alexander Larsson
2008-10-10 22:18 ` Szabolcs Szakacsits
2008-10-10 22:21 ` Nicolò Chieffo
2008-10-10 22:25 ` Christoph Hellwig
2008-10-10 22:33 ` Nicolò Chieffo
2008-10-10 22:36 ` Christoph Hellwig
2008-10-10 22:58 ` Nicolò Chieffo
2008-10-10 23:12 ` Szabolcs Szakacsits
2008-10-11 0:10 ` Bryan Henderson
2008-10-11 1:36 ` Theodore Tso
2008-10-10 22:57 ` Brad Boyer
2008-10-13 7:29 ` Anton Altaparmakov
2008-10-13 10:47 ` Christoph Hellwig
2008-10-13 10:59 ` Alexander Larsson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081010192104.GD19500@unused.rdu.redhat.com \
--to=jbacik@redhat.com \
--cc=84yelo3@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox