I am also having some trouble with the latest version of Cygwin, which includes
this patch.
See
http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html
for example.
I am having a related issue, with C++ code that parses the command line.
The command line we support is something like -
prog
Prakash Babu wrote:
thanks Christopher.
I found the following archive which introduced this fix
(http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html)
I've read this thread, and I'm not convinced that the path improves the
behavior. You seem to have traded one inconsistency with anothe
Greetings, Prakash Babu!
> thanks Christopher.
> I found the following archive which introduced this fix
> (http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html)
> I feel this causes an inconsistent behavior when batch scripts are
> executed using command interpreter(cmd.exe) and cygwin.
>
thanks Christopher.
I found the following archive which introduced this fix
(http://cygwin.com/ml/cygwin-patches/2014-q1/msg00017.html)
I feel this causes an inconsistent behavior when batch scripts are
executed using command interpreter(cmd.exe) and cygwin.
There are some generic batch script we
On Sun, Feb 16, 2014 at 10:35:32PM -0500, Christopher Faylor wrote:
>On Mon, Feb 17, 2014 at 08:05:45AM +0530, Prakash Babu wrote:
>>Was there any reason why just =(equalto) was removed as a command line
>>separator for cygwin 1.7.28 , while the other delimiters like comma
>>are still supported ? T
On Mon, Feb 17, 2014 at 08:05:45AM +0530, Prakash Babu wrote:
>Was there any reason why just =(equalto) was removed as a command line
>separator for cygwin 1.7.28 , while the other delimiters like comma
>are still supported ? This is causing existing batch files that use
>equalto(=) as a command li
thanks Christopher for your response.
This is the observation I made wrt to the command line delimiters for
batch files.
cmd.exe delimiters
==
space,
equalto(=)
semicolon (;)
comma(,)
cygwin 1.7.27 delimiters
==
space
quotes("")
equalto(=)
comma(,)
cygwin 1.7.28 deli
On Fri, Feb 14, 2014 at 12:10:00PM +0530, Prakash Babu wrote:
>Hi ,
>
>
>I use Cygwin to execute batch scripts on remote windows hosts using ssh.
>
>The batch script execution started failing with the latest cygwin
>version 1.7.28.
>
>The exit code thrown is 255 and batch script is not able to proc
Greetings, Prakash Babu!
> I use Cygwin to execute batch scripts on remote windows hosts using ssh.
> The batch script execution started failing with the latest cygwin
> version 1.7.28.
> The exit code thrown is 255 and batch script is not able to process
> the command line arguments.
> When I
Hi ,
I use Cygwin to execute batch scripts on remote windows hosts using ssh.
The batch script execution started failing with the latest cygwin
version 1.7.28.
The exit code thrown is 255 and batch script is not able to process
the command line arguments.
When I try to print the command line a
10 matches
Mail list logo
