Date: Tue, 19 Dec 2000 13:49:04 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: kredba <kredba AT mbox DOT dkm DOT cz>
cc: djgpp AT delorie DOT com
Subject: Re: "Command line too long"
In-Reply-To: <000b01c069ad$db54cb80$6048183e@ghu>
Message-ID: <Pine.SUN.3.91.1001219134522.365Q-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 19 Dec 2000, kredba wrote:

> If you are running MS Windows, you can run rhide.exe from desktop in MSDOS
> window. It means that windows run rhide.pif  and from rhide.pif
> "command /c rhide.exe" or you can call it directly from MSDOS window.

This will change nothing.

> MSDOS window is limited to 128 chars at command prompt. You can call command
> /U:255 /E:4096 (U size of command line in chars, E size of environment in
> bytes) to run MSDOS command prompt or try run bash.exe as command
> interpreter.

This is irrelevant: RHIDE invokes the compiler directly, not through any 
shell, and it uses the special way of passing command lines between DJGPP 
programs, which is not limited by 126 (not 128) characters, and is not 
affected by the COMMAND.COM's /U and /E switches.

> Bash
> 2.04 has probably bug. While runnig long command lines - it causes E2BIG
> errors

Please post an example command line that can be used to reproduce this 
bug.