Re: psql \e broken again

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
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:10:39
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCE476162@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> >> Agreed, no quotes on Unix. I'm just wondering what to do
> on Windows.
>
> > I would require the user to add quotes around his
> executable if it has
> > spaces.
>
> > set EDITOR="C:/Program Files/vim/vim63/gvim.exe" -y
>
> I think this policy is OK for the Mac OS X case, but I am
> wondering if it will cause any compatibility problems on
> Windows. In particular, if other programs expect to
> double-quote EDITOR themselves, then there'd be no way to
> make the same value work for both PG and the others.

I don't think I've seen a single windows program that uses the EDITOR
variable. There are some ported unix tools, but that's it. Native
windows program will have a per-program setting for this. The system
default is picked based on file extension. So I doubt it will break a
lot of things.

If we're very worried about this, how about using PGEDITOR instead of
EDITOR?

//Magnus

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2004-11-15 16:13:15 Re: psql \e broken again
Previous Message Simon Riggs 2004-11-15 16:01:27 Re: Database reverse engineering