Re: First UI component needing replacement.

[Ken Fox <kfox vulpes com>]

Christian Rose wrote:
> I'd rather not brake compability with everything else just so that space
> can be used as a shortcut key.

I've never said that spaces would break things. There is a problem in
entering a file name for *output* if the space is in an ambiguous
location. If <*> were used as the key binding instead of <space> I
suppose that would make everybody happy? (Except for me who would
rather hit a big key than a shifted little key... ;)

> Heck, even good ol' bash handles file names with spaces right. Imagine
> the headlines if Gnome suddenly doesn't?

We don't need to use escape sequences like bash. And spaces wouldn't
break things, so I suppose we'd sue for libel. ;)

> On the other hand, "?" is used as a wildcard key on both Linux and
> Windows, and isn't a permitted file name character on either of them
> last time I checked.

All characters except nil (\0) and "/" are legal file characters
on Linux. I don't know about Windows.

> But it should be used for regexps, not for keyboard
> shortcuts, when it's a file dialog that will support regexps eventually.

And the regexps should not come anywhere near the file *name* field.
The file name is the area where we build up the *result* of the file
dialog. Whatever is in that field when I hit OK gets sent to the app.
 
> Tab isn't a valid filename character. Space is.

See above. The difference here is that you don't use the tab character
in your file names so you don't think it matters. I don't use the
space in my file names. I'm willing to compromise and say use the <*>
key.

- Ken