all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nix <nix@esperi.org.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Deniz Dogan <deniz@dogan.se>, emacs-devel@gnu.org
Subject: Re: VC and too long command lines
Date: Fri, 22 Jul 2011 21:37:50 +0100	[thread overview]
Message-ID: <87mxg6jbkx.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <83hb6fva64.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jul 2011 20:02:59 +0300")

On 21 Jul 2011, Eli Zaretskii said:

>> Date: Thu, 21 Jul 2011 16:16:17 +0200
>> From: Deniz Dogan <deniz@dogan.se>
>> 
>> Do you happen to know of any reliable way to determine the maximum
>> command line length of the user system?
>
> There isn't any, AFAIK.

There is, but it's time-consuming. Repeatedly retry a longer and longer
harmless command until one fails. (libtool does it.)

(Note that just because a command succeeds doesn't mean a later one
won't fail: many Unix systems have a fixed length for
cmdline+environment, so if the environment grows then the command-line
space necessarily must shrink. So this probably isn't actually much use
because it means we can't check in advance, and it's too slow to check
at the time. I suppose we could check in advance, and only recheck if
someone calls `setenv'...)

-- 
NULL && (void)



  reply	other threads:[~2011-07-22 20:37 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mxg6jbkx.fsf@spindle.srvr.nix \
    --to=nix@esperi.org.uk \
    --cc=deniz@dogan.se \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.