From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: cosmetic completion problem
Date: Mon, 10 Oct 2005 14:06:36 +0000 [thread overview]
Message-ID: <1051010140636.ZM13471@candle.brasslantern.com> (raw)
In-Reply-To: <EXCHANGE03O6AprLfKY00003f28@exchange03.csr.com>
On Oct 10, 10:37am, Peter Stephenson wrote:
}
} What might be more interesting is that I changed
}
} if (++col == columns) {
} into
} if (col >= columns) {
}
} which might well have introduced a subtle bug.
No, that's another red herring. The non-unicode branch still has the
original ++col and I get the crash with --disable-multibyte. I think
the real bug happens somewhere outside this function, before execution
even gets this far.
prev parent reply other threads:[~2005-10-10 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-06 20:58 Clint Adams
2005-10-08 7:32 ` DervishD
2005-10-08 21:40 ` Clint Adams
2005-10-09 2:54 ` Bart Schaefer
2005-10-10 9:37 ` Peter Stephenson
2005-10-10 14:06 ` 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=1051010140636.ZM13471@candle.brasslantern.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).