zsh-workers
 help / color / mirror / code / Atom feed
From: Clint Adams <clint@zsh.org>
To: zsh-workers@sunsite.dk, Falk Hueffner <falk@debian.org>,
	283358@bugs.debian.org
Subject: Re: Bug#283358: echo $((##)) overflows buffer
Date: Sun, 28 Nov 2004 11:23:14 -0500	[thread overview]
Message-ID: <20041128162314.GA9718@scowler.net> (raw)
In-Reply-To: <20041128162404.GA809@DervishD>

>     Doesn't happen in 4.0.9... It always prints '0'. Should I try
> to set some option to reproduce?
> 
>     Raúl Núñez de Arenas Coronado

This is only happening on Alphas, it would seem.


  reply	other threads:[~2004-11-28 16:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1CYOp6-00082T-PR@juist>
2004-11-28 16:10 ` Clint Adams
2004-11-28 16:24   ` DervishD
2004-11-28 16:23     ` Clint Adams [this message]
2004-11-29 11:58   ` Peter Stephenson
2004-11-30 16:31     ` Clint Adams

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=20041128162314.GA9718@scowler.net \
    --to=clint@zsh.org \
    --cc=283358@bugs.debian.org \
    --cc=falk@debian.org \
    --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).