[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: VC and too long command lines
From: |
Nix |
Subject: |
Re: VC and too long command lines |
Date: |
Fri, 22 Jul 2011 21:37:50 +0100 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (gnu/linux) |
On 21 Jul 2011, Eli Zaretskii said:
>> Date: Thu, 21 Jul 2011 16:16:17 +0200
>> From: Deniz Dogan <address@hidden>
>>
>> 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)
- VC and too long command lines, Deniz Dogan, 2011/07/21
- Re: VC and too long command lines, Eli Zaretskii, 2011/07/21
- Re: VC and too long command lines, Deniz Dogan, 2011/07/21
- Re: VC and too long command lines, Eli Zaretskii, 2011/07/21
- Re: VC and too long command lines,
Nix <=
- Re: VC and too long command lines, Eli Zaretskii, 2011/07/23
- Re: VC and too long command lines, Richard Stallman, 2011/07/23
- Re: VC and too long command lines, Eli Zaretskii, 2011/07/23
- Re: VC and too long command lines, Nix, 2011/07/23
Re: VC and too long command lines, Daniel Colascione, 2011/07/21