From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: psql \e broken again |
Date: | 2004-11-15 16:13:15 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE476163@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > We could maybe compromise with (again, for Windows only) a
> policy like
> > "double-quote unless the value already contains at least one
> > double-quote". This should work conveniently for everybody
> except the
> > user who wants EDITOR='gvim.exe -y' on Windows; he'll have
> to add some
> > useless-looking double quotes a la EDITOR='"gvim.exe" -y'.
>
> Single quotes don't work on Windows (tried with %EDITOR%
> x.txt). I think we should not worry too much since the user
> could use the "good old"
> EDITOR=C:/PROGRA~1/vim/vim63/gvim.exe -y syntax on win if all
> else fails.
No we can't assume people can do that :-)
Anybody who's running at least a server for max file performance (or
when you're talking a web server in some cases certainly for security as
well) run with 8.3 filenames turned off per
http://support.microsoft.com/kb/121007.
It's not uncommon to see this pushed out with Group Policy as well.
//Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-11-15 16:13:51 | Re: psql \e broken again |
Previous Message | Magnus Hagander | 2004-11-15 16:10:39 | Re: psql \e broken again |