On Thu, 2007-02-22 at 17:39 -0500, Sean Middleditch wrote:
Just a reminder that : is the separator used in the PATH environment
variable, and is thus a poor choice for use in directories.
In all honesty, if the intended use case for reading the directory info
is for FUSE and GVFS, I think it
Just a reminder that : is the separator used in the PATH environment
variable, and is thus a poor choice for use in directories.
In all honesty, if the intended use case for reading the directory info
is for FUSE and GVFS, I think it would be a lot cleaner to just put some
kind of user-friendly
On Thu, 2007-02-22 at 12:49 -0600, Hans Petter Jansson wrote:
On Thu, 2007-02-22 at 12:38 +, Damon Chaplin wrote:
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
However, the first method you describe:
On Thu, 2007-02-22 at 14:22 -0600, Hans Petter Jansson wrote:
On Thu, 2007-02-22 at 13:51 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 12:38 +, Damon Chaplin wrote:
You're probably always going to need type, server and share though, so
maybe you can make it a bit more
On Thu, 2007-02-22 at 14:51 -0600, Hans Petter Jansson wrote:
On Thu, 2007-02-22 at 14:44 +0100, Alexander Larsson wrote:
In fact, its likely they implement this by just stat()ing all the files
in the recent list. This is a great example of where automounting would
royaly screw things up.
On Thu, 2007-02-22 at 22:26 +0100, Nikolai Weibull wrote:
On 2/22/07, Hans Petter Jansson [EMAIL PROTECTED] wrote:
~/.mounts/type=smb-share;server=$server;share=$share/dir/file.txt
I just want to point out that there's a freedesktop specification for
where things should be stored. Not
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
This won't work. We need to be able to extract all the mount information
from the path, so that if the app stores the path across sessions, say,
in recent documents, the FUSE layer will know what to do when it's
accessed later.
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
However, the first method you describe:
~/.mounts/type=smb-share;server=$server;share=$share/dir/file.txt
sounds perfect. It's rich (we can get back the mount info later),
extensible (we don't have to figure out the entire set
On Thu, 2007-02-22 at 10:33 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
This won't work. We need to be able to extract all the mount information
from the path, so that if the app stores the path across sessions, say,
in recent documents,
On Thu, 2007-02-22 at 12:38 +, Damon Chaplin wrote:
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
However, the first method you describe:
~/.mounts/type=smb-share;server=$server;share=$share/dir/file.txt
sounds perfect. It's rich (we can get back the mount info
On Thu, 2007-02-22 at 13:49 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 10:33 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
This won't work. We need to be able to extract all the mount information
from the path, so that if the
On Thu, 2007-02-22 at 12:38 +, Damon Chaplin wrote:
On Thu, 2007-02-22 at 03:10 -0600, Hans Petter Jansson wrote:
However, the first method you describe:
~/.mounts/type=smb-share;server=$server;share=$share/dir/file.txt
sounds perfect. It's rich (we can get back the mount info
On Thu, 2007-02-22 at 13:51 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 12:38 +, Damon Chaplin wrote:
You're probably always going to need type, server and share though, so
maybe you can make it a bit more readable:
~/.mounts/smb:$server:$share/dir/file.txt
Extra
On Thu, 2007-02-22 at 14:44 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 13:49 +0100, Alexander Larsson wrote:
On Thu, 2007-02-22 at 10:33 +0100, Alexander Larsson wrote:
As a further example of this I tried OSX. It has a system similar to the
first proposal. I.E. When you mount
On 2/22/07, Hans Petter Jansson [EMAIL PROTECTED] wrote:
~/.mounts/type=smb-share;server=$server;share=$share/dir/file.txt
I just want to point out that there's a freedesktop specification for
where things should be stored. Not many seem to respect it, but I,
for one, really would appreciate
15 matches
Mail list logo
