Re: psql \e broken again

From: "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Peter Eisentraut" <peter_e(at)gmx(dot)net>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql \e broken again
Date: 2004-11-15 08:46:11
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184D228@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Mike Rylander 2004-11-15 11:36:29 Re: Odd plpgsql behaviour
Previous Message Dawid Kuroczko 2004-11-15 07:55:32 Re: MAX/MIN optimization via rewrite (plus query rewrites