>> I like Kevin Brown's suggestion of writing out a temporary .txt file and
>> 'executing' it. It will follow the principle of least suprise for Windows
>> users.
>
> Note that the current default behavior (assuming you've not set EDITOR)
> is "vi foo.txt" which is quite unlikely to be helpful to a
"Bort, Paul" <[EMAIL PROTECTED]> writes:
> I like Kevin Brown's suggestion of writing out a temporary .txt file and
> 'executing' it. It will follow the principle of least suprise for Windows
> users.
Note that the current default behavior (assuming you've not set EDITOR)
is "vi foo.txt" which is
Title: RE: [HACKERS] psql \e broken again
From: Zeugswetter Andreas DAZ SD [mailto:[EMAIL PROTECTED]]
>
> 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
>
>> 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
Tom Lane wrote:
> "Magnus Hagander" <[EMAIL PROTECTED]> writes:
> >> Agreed, no quotes on Unix. I'm just wondering what to do
> >> on Windows.
>
> > 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
> > win
"Bort, Paul" <[EMAIL PROTECTED]> writes:
> The one that I see most often ( and use here ) is CVSGUI (
> http://www.wincvs.org/ ), which includes a CVS command-line client despite
> the name. ( The command-line CVS might be from CVSNT,
> http://www.cvsnt.com/cvspro/ ).
> So I thought I'd try a few
Title: RE: [HACKERS] psql \e broken again
From: Peter Eisentraut [mailto:[EMAIL PROTECTED]]
>
> Is there a Windows port of the command-line cvs tool? That
> would be a
> good thing to compare with.
>
The one that I see most often ( and use here ) is CVSGUI ( http:/
Peter Eisentraut wrote:
Magnus Hagander wrote:
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
Magnus Hagander wrote:
> 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 b
> > 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 so
> >> Agreed, no quotes on Unix. I'm just wondering what to do
> on Windows.
>
> > 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
"Magnus Hagander" <[EMAIL PROTECTED]> writes:
>> Agreed, no quotes on Unix. I'm just wondering what to do
>> on Windows.
> 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-p
> >> 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
> wo
> 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-lookin
"Zeugswetter Andreas DAZ SD" <[EMAIL PROTECTED]> writes:
>> 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
On Sun, Nov 14, 2004 at 10:14:06PM -0500, Bruce Momjian wrote:
John Hansen wrote:
1. Quote only on Windows.
2. Expect user to put quotes in the EDITOR value if it contains a
space-containing path.
As far I I'm aware, the options on windows are very much like those on
unix:
"path containing spaces"
>> 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
hi,
As for mac os x this is on darwin mac os (it's mac something)
I ran a find command with a space in it.
mechatronics:~ joe$ find . -name '* *'
./backups/dscpadmin/scriptsMay19/dscp/validate/List of Cancers.doc
./backups/pain/PAINjune/validate/List of Cancers.doc
./backups/untarhere/test/List o
John Hansen wrote:
> > > 1. Quote only on Windows.
> > >
> > > 2. Expect user to put quotes in the EDITOR value if it contains a
> > > space-containing path.
>
>
> As far I I'm aware, the options on windows are very much like those on
> unix:
>
> "path containing spaces" or
> path\ containing\
> > 1. Quote only on Windows.
> >
> > 2. Expect user to put quotes in the EDITOR value if it contains a
> > space-containing path.
As far I I'm aware, the options on windows are very much like those on
unix:
"path containing spaces" or
path\ containing\ spaces
Kind Regards
John Hansen
--
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> 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 t
Tom Lane wrote:
> I think the rationale was to allow paths containing spaces, which is
> a pretty serious problem on Windows. Seems like we have two basic
> options:
>
> 1. Quote only on Windows.
>
> 2. Expect user to put quotes in the EDITOR value if it contains a
> space-containing path.
The ED
Peter Eisentraut <[EMAIL PROTECTED]> writes:
> A remember specifically that I somewhat recently fixed psql to accept
> editors with arguments, say EDITOR="pico -t". This was apparently
> broken again during some Windows-related reshuffling. It now takes the
> editor as one quoted string rather
A remember specifically that I somewhat recently fixed psql to accept
editors with arguments, say EDITOR="pico -t". This was apparently
broken again during some Windows-related reshuffling. It now takes the
editor as one quoted string rather than possibly several shell tokens.
Could this ple
24 matches
Mail list logo
