open and backslashes...
From: Jeff Godfrey (jeff_godfrey_at_pobox.com)
Date: 03/25/05
- Next message: Jeff Godfrey: "Re: open and backslashes..."
- Previous message: ramesh venk: "Oratcl 4.3 fails to initialize on Solaris with Oracle 9"
- Next in thread: Jeff Godfrey: "Re: open and backslashes..."
- Reply: Jeff Godfrey: "Re: open and backslashes..."
- Reply: Don Porter: "Re: open and backslashes..."
- Reply: Gerald W. Lester: "Re: open and backslashes..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Fri, 25 Mar 2005 13:03:25 -0600
Hi All,
Under WinXP, given a user supplied program command line, such as:
set cmd {c:\path\to\myprog.exe -F 1 -G 2:2 -Q "a text parm"}
What is the best/safest way to make the above "acceptable" to the open
command, as in:
open "|$cmd"
It seems that I need to convert the (possible) backslashes in the exe path
to forward slashes for open, but I don't want to break anything else in the
supplied command line. Also, I suppose the exe path could contain spaces...
I've managed to kludge my way through the above issue several times in the
past, but am wondering if there is a canonical way of accomplishing this?
Thanks for any suggestions.
Jeff
- Next message: Jeff Godfrey: "Re: open and backslashes..."
- Previous message: ramesh venk: "Oratcl 4.3 fails to initialize on Solaris with Oracle 9"
- Next in thread: Jeff Godfrey: "Re: open and backslashes..."
- Reply: Jeff Godfrey: "Re: open and backslashes..."
- Reply: Don Porter: "Re: open and backslashes..."
- Reply: Gerald W. Lester: "Re: open and backslashes..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|