zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: number of arguments zargs use
Date: Wed, 3 Nov 2004 17:32:28 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.61.0411031731050.470@toltec.zanshin.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0410302124550.21138@toltec.zanshin.com>

On Sat, 30 Oct 2004, Bart Schaefer wrote:

> s=${${s##-(s|-max-chars(=|))}:-$(((s=$({command getconf ARG_MAX ||
>     command sysctl -n kern.argmax || echo 0} 2>/dev/null))?
>     (s-=${#$(builtin typeset +x)}+2048):20480))}

Just in case anyone tries this, there's a typo: +x should be -x.


      parent reply	other threads:[~2004-11-04  1:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-30 13:59 Motoi Washida
2004-10-31  5:30 ` Bart Schaefer
2004-10-31  7:34   ` Motoi Washida
2004-11-04  1:32   ` Bart Schaefer [this message]

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=Pine.LNX.4.61.0411031731050.470@toltec.zanshin.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).