From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: Core dump with latest CVS
Date: Fri, 15 Sep 2006 16:36:53 +0100 [thread overview]
Message-ID: <200609151536.k8FFar2G018941@news01.csr.com> (raw)
In-Reply-To: <060915081653.ZM9804@torch.brasslantern.com>
Bart Schaefer wrote:
> My concern is that "printability" shouldn't have anything to do with it.
> Programmatically, the expression
>
> (( ${#:-X} == 1 && ${#(pl.width..X.)} == width ))
>
> should always be true.
OK, you're interpreting "width" differently... to me, that's a string
length, not a width at all. It doesn't really matter as long as it's
documented.
So that would be the last option I posted, treat multibyte characters
but assume they have width 1 (or, in better English, use string lengths
rather than character widths for padding) unless there's an additional
flag. I would propose to supply such a flag, if we go this way.
> I could see an argument that ${#(%pl.width.X)} could compute the padding
> based on printable width, because the presence of % means we're expanding
> prompt escapes so presumably we want printable values
I don't really see why a normal user would assume the expression
*didn't* deal with printable widths, but, again, that's mostly a matter
of documentation.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
prev parent reply other threads:[~2006-09-15 15:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-14 21:02 Vin Shelton
2006-09-15 9:57 ` Peter Stephenson
2006-09-15 10:15 ` Peter Stephenson
2006-09-15 13:08 ` Peter Stephenson
2006-09-15 15:16 ` Bart Schaefer
2006-09-15 15:36 ` Peter Stephenson [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=200609151536.k8FFar2G018941@news01.csr.com \
--to=pws@csr.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).