Re: a GtkFileChooser comment

[Daniel Brockman <drlion deepwood net>]

Jonathan Blandford <jrb redhat com> writes:

> Sven Neumann <sven gimp org> writes:

[snip]

> Also, as you say '~' and '..' are valid starting paths for files
> (eg. "~200-250 recipes.txt", "...And Justice For All.mp3").
> Currently, you can type the first couple letters of a file and hit
> enter -- I don't know how you'd distinguish between wanting the home
> dir in one case and the file in the other.

While I agree that adding additional meanings for `~' and `..' would
slightly increase ambiguity, the ambiguity already exists:  You can
have one file named `foo', and another named `foobar' --- or even one
named `~'!

> > Such a change would make the Ctrl-L window unnecessary for
> > keyboard users. It should probably be kept around and bound to
> > Ctrl-L but I think the goal should be to obsolete it. Thus the
> > current '/' binding appears to be a step into the wrong direction.
>
> It's possible that '/' opening the dialog is misguided, it was added
> on more of a whim.  I was thinking along the lines of it being
> similar to '/' being used for find in mozilla.  Additionally, if
> you're typing '/', you're opening for an absolute path which means
> you know it's full location.  The C-l dialog seems better suited for
> that case.

The user typing a `/' is by no means conclusive evidence of their
knowing the full path name, just as their typing `~' isn't.


Regards,

-- 
Daniel Brockman
drlion deepwood net