From: Jeff G. <jef...@po...> - 2003-09-10 14:44:01
|
Hi All, My company has a multi-platform (Win* and *nix) software product that accepts command line arguments. When the product is started on a PC through the MSYS BASH shell, our software is receiving a trailing space after the last command line argument. Now, that's easily fixed within our software by trimming the entire command line string before processing (which we've done), but I'm curious where the space is coming from? We have never experienced this problem with any other shell on any platform (DOS shell, MKS Toolkit Korn shell, various standard Unix shells, etc...) We are currently using MSYS 1.0.9 Any ideas? Thanks, Jeff |
From: Earnie B. <ea...@us...> - 2003-09-11 12:14:08
|
Jeff Godfrey wrote: > Hi All, > > My company has a multi-platform (Win* and *nix) software product that > accepts command line arguments. When the product is started on a PC through > the MSYS BASH shell, our software is receiving a trailing space after the > last command line argument. Now, that's easily fixed within our software by > trimming the entire command line string before processing (which we've > done), but I'm curious where the space is coming from? We have never > experienced this problem with any other shell on any platform (DOS shell, > MKS Toolkit Korn shell, various standard Unix shells, etc...) > > We are currently using MSYS 1.0.9 > > Any ideas? > I think (and I've not had much time to do that for MinGW or MSYS recently) that the problem is with RXVT port. You can confirm this by renaming the rxvt binary from the windows file explorer and then starting the MSYS process via the icon. This will cause sh to execute from the cmd window. Thanks, Earnie. |
From: Jeff G. <jef...@po...> - 2003-09-13 13:13:48
|
Hi Earnie, I just tried your suggestion. While it appears the shell does execute from the command window like you said, the trailing space still exists. Any other thoughts? Thanks, Jeff ----- Original Message ----- From: "Earnie Boyd" <ea...@us...> To: <min...@li...> Sent: Thursday, September 11, 2003 7:12 AM Subject: Re: [Mingw-msys] trailing space on MSYS command line? > Jeff Godfrey wrote: > > Hi All, > > > > My company has a multi-platform (Win* and *nix) software product that > > accepts command line arguments. When the product is started on a PC through > > the MSYS BASH shell, our software is receiving a trailing space after the > > last command line argument. Now, that's easily fixed within our software by > > trimming the entire command line string before processing (which we've > > done), but I'm curious where the space is coming from? We have never > > experienced this problem with any other shell on any platform (DOS shell, > > MKS Toolkit Korn shell, various standard Unix shells, etc...) > > > > We are currently using MSYS 1.0.9 > > > > Any ideas? > > > > I think (and I've not had much time to do that for MinGW or MSYS > recently) that the problem is with RXVT port. You can confirm this by > renaming the rxvt binary from the windows file explorer and then > starting the MSYS process via the icon. This will cause sh to execute > from the cmd window. > > Thanks, > Earnie. > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > > |
From: Earnie B. <ea...@us...> - 2003-09-15 12:15:03
|
Not at present. Could you attach a sample program that demonstrates the bug so I know when it is fixed please. Earnie. Jeff Godfrey wrote: > Hi Earnie, > > I just tried your suggestion. While it appears the shell does execute from > the command window like you said, the trailing space still exists. Any > other thoughts? > > Thanks, > > Jeff > > > ----- Original Message ----- > From: "Earnie Boyd" <ea...@us...> > To: <min...@li...> > Sent: Thursday, September 11, 2003 7:12 AM > Subject: Re: [Mingw-msys] trailing space on MSYS command line? > > > >>Jeff Godfrey wrote: >> >>>Hi All, >>> >>>My company has a multi-platform (Win* and *nix) software product that >>>accepts command line arguments. When the product is started on a PC > > through > >>>the MSYS BASH shell, our software is receiving a trailing space after > > the > >>>last command line argument. Now, that's easily fixed within our > > software by > >>>trimming the entire command line string before processing (which we've >>>done), but I'm curious where the space is coming from? We have never >>>experienced this problem with any other shell on any platform (DOS > > shell, > >>>MKS Toolkit Korn shell, various standard Unix shells, etc...) >>> >>>We are currently using MSYS 1.0.9 >>> >>>Any ideas? >>> >> >>I think (and I've not had much time to do that for MinGW or MSYS >>recently) that the problem is with RXVT port. You can confirm this by >>renaming the rxvt binary from the windows file explorer and then >>starting the MSYS process via the icon. This will cause sh to execute >>from the cmd window. >> >>Thanks, >>Earnie. >> >> >> >>------------------------------------------------------- >>This sf.net email is sponsored by:ThinkGeek >>Welcome to geek heaven. >>http://thinkgeek.com/sf >>_______________________________________________ >>Mingw-msys mailing list >>Min...@li... >>https://lists.sourceforge.net/lists/listinfo/mingw-msys >> >> > > > > > ------------------------------------------------------- > This sf.net email is sponsored by:ThinkGeek > Welcome to geek heaven. > http://thinkgeek.com/sf > _______________________________________________ > Mingw-msys mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-msys > |