From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: VC and too long command lines
Date: Sat, 23 Jul 2011 18:18:37 +0100 [thread overview]
Message-ID: <87oc0kj4pe.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83zkk5cl5g.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 23 Jul 2011 14:05:15 +0300")
On 23 Jul 2011, Eli Zaretskii uttered the following:
>> Date: Sat, 23 Jul 2011 06:36:40 -0400
>> From: Richard Stallman <rms@gnu.org>
>> CC: emacs-devel@gnu.org
>>
>> However, it might be better to make a conservative assumption about
>> how big the command line can be, and always keep generated commands
>> under that size.
>
> In my experience, 30K bytes is such a conservative assumption on
> MS-Windows.
Unfortunately on operating systems that share the environment and
command line, the maximum command line length can get *very* small, and
of course can vary. I recall HP-UX 10.20 refusing to run anything
because the environment was 8190 bytes... and on that system we
regularly had environments >8000 bytes, so things broke all the time :(
(I too would be fascinated to learn of other constraints on command-line
length on Windows. I suspect the Libtool people might like to know as
well.)
--
NULL && (void)
next prev parent reply other threads:[~2011-07-23 17:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-21 12:55 VC and too long command lines Deniz Dogan
2011-07-21 14:12 ` Eli Zaretskii
2011-07-21 14:16 ` Deniz Dogan
2011-07-21 17:02 ` Eli Zaretskii
2011-07-22 20:37 ` Nix
2011-07-23 7:05 ` Eli Zaretskii
2011-07-23 10:36 ` Richard Stallman
2011-07-23 11:05 ` Eli Zaretskii
2011-07-23 17:18 ` Nix [this message]
2011-07-21 14:16 ` Daniel Colascione
2011-08-02 3:48 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oc0kj4pe.fsf@spindle.srvr.nix \
--to=nix@esperi.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).