On 10/27/2015 09:10 AM, Dr Rainer Woitok wrote:
> Eric,
>
> On Monday, 2015-10-26 10:14:06 -0600, you wrote:
>
>> ...
>> So once
>> you start a dash shell, that dash shell can start any number of other
>> dash shells with no command
Corinna,
On Tuesday, 2015-10-27 16:17:56 +0100, you wrote:
> ...
> That won't work. setup.exe is a non-Cygwin application so it's restricted
> to the maximum line length of the CreateProcess call, which, per
> https://msdn.microsoft.com/en-us/library/windows/desktop/ms682425%28v=vs.85%29.aspx
>
On Oct 27 16:10, Dr Rainer Woitok wrote:
> Eric,
>
> On Monday, 2015-10-26 10:14:06 -0600, you wrote:
>
> > ...
> > So once
> > you start a dash shell, that dash shell can start any number of other
> > dash shells with no command li
Eric,
On Monday, 2015-10-26 10:14:06 -0600, you wrote:
> ...
> So once
> you start a dash shell, that dash shell can start any number of other
> dash shells with no command line length limit other than the memory
> available to your
On 10/26/2015 05:16 AM, Dr Rainer Woitok wrote:
> Does anybody definitely know about a maximum command line length in the
> Ash or Dash Shells?
/bin/ash _is_ the same as /bin/dash, so there is no difference in their
behavior.
A windows process spawning a cygwin one, or a cygwin process spawning
Fellow Cygwinners,
recently I needed to remove quite a few Cygwin packages from my install-
ation, and due to all these interdependencies I wanted to do this in a
single call:
setup-x86*.exe -x ...,...,...
Calling this command as a Windows "*.bat" file failed with an error
message sugg
6 matches
Mail list logo
