Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Core dump with latest CVS
- X-seq: zsh-workers 22712
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx (Zsh hackers list)
- Subject: Re: Core dump with latest CVS
- Date: Fri, 15 Sep 2006 08:16:53 -0700
- In-reply-to: <200609151308.k8FD8IGQ025083@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20a807210609141402v31714a98wab9b75ff7736327@xxxxxxxxxxxxxx> <200609150957.k8F9v4uq021513@xxxxxxxxxxxxxx> <200609151308.k8FD8IGQ025083@xxxxxxxxxxxxxx>
On Sep 15, 2:08pm, Peter Stephenson wrote:
}
} I'll commit this pair of changes for now, since it fixes the crash and
} mostly does the right thing transparently---ASCII characters behave as
} they used to and multibyte characters as they should---but if there are
} strong views I can change it.
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.
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 ... but there is
a reason that %{ %} has to be placed around non-printing sequences in
prompts.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author