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>, "Bort, Paul" <pbort(at)tmwsystems(dot)com>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: psql \e broken again
Date: 2004-11-16 11:14:43
Message-ID: 46C15C39FEB2C44BA555E356FBCD6FA40184D22D@m0114.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


>> So I thought I'd try a few scenarios, since I have it installed:
>> [ none of which work ]
>> So to answer your question, at least in part, there is no current good
>> behavior to emulate. At least on this version of CVS:

> I think this is fairly graphic proof that (1) a straight port without
> doing anything special is essentially nonfunctional on Windows, and that
> (2) there isn't any easy way for the user to fix it by inserting quotes
> for himself.

I am not sure the test is valid, since %EDITOR% was used on the command line,
which does it's own magic on quotes. Is there a command that would use the
envvar EDITOR without putting it on the commandline ?

We are talking about directly using the envvar from inside the program, no?

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Roberto Fichera 2004-11-16 14:37:31 pg_dump problem
Previous Message Kevin Brown 2004-11-16 10:51:54 Re: psql \e broken again