Re: [PATCHES] psql \! WIN32 cleanup - Mailing list pgsql-hackers-win32

From John A Meinel
Subject Re: [PATCHES] psql \! WIN32 cleanup
Date
Msg-id 418C6AE9.5060300@johnmeinel.com
Whole thread Raw
List pgsql-hackers-win32
Bruce Momjian wrote:
> Tom Lane wrote:
>
>>Bruce Momjian <pgman@candle.pha.pa.us> writes:
>>
>>>The attached applied patch tests for COMSPEC in the right place and
>>>supplies a reasonable shell default on Win32.
>>
>>>+ #define DEFAULT_SHELL "c:/windows/system32/cmd.exe"
>>
>>Is it really a good idea to assume that the Windows installation is on
>>drive C: ?
>>
>>(This is an honest question, not a rhetorical one.  I dunno whether
>>inserting the C: is better than leaving it off.  I can think of cases
>>where either way will break, but I'm unsure what's most likely in
>>practice.)
>
>
> Not sure.  Should we just do "/windows/system32/cmd.exe" and leave off
> the C:?  The previous default was "/bin/sh" and that certainly will not
> work on Win32.
>

Do you need to supply the full path to the executable? Because if it is
in the system PATH, then it should be found, and you can just do:

#define DEFAULT_SHELL "cmd.exe"

Or, if you allow environment variables, then something like:

#define DEFAULT_SHELL "$WINDIR/system32/cmd.exe"

is probably the way to go.

John
=:->

Attachment

pgsql-hackers-win32 by date:

Previous
From: Aleksander Kmetec
Date:
Subject: locales and encodings on Windows
Next
From: Reini Urban
Date:
Subject: [Fwd: PostgreSQL 8.0.0-beta4 Windows 2000 Installation]