Re: psql \e broken again - Mailing list pgsql-hackers

From Zeugswetter Andreas DAZ SD
Subject Re: psql \e broken again
Date
Msg-id 46C15C39FEB2C44BA555E356FBCD6FA40184D228@m0114.s-mxs.net
Whole thread Raw
In response to psql \e broken again  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: psql \e broken again  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
>> The EDITOR variable seems to have a fairly standard meaning on Unix
>> systems.  I've been using that EDITOR value for years without problems,
>> only when I use psql's \e once in a while it breaks.  I don't think we
>> should deviate from what seems to be a standard practice.
>
> 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

Andreas


pgsql-hackers by date:

Previous
From: Dawid Kuroczko
Date:
Subject: Re: MAX/MIN optimization via rewrite (plus query rewrites
Next
From: Mike Rylander
Date:
Subject: Re: Odd plpgsql behaviour