From: Sebastian Gniazdowski <psprint3@fastmail.com>
To: zsh-workers@zsh.org
Subject: Re: (m)-flag for boundary cases
Date: Mon, 20 Mar 2017 09:00:46 -0700 [thread overview]
Message-ID: <1490025646.2635901.917311768.731A36CF@webmail.messagingengine.com> (raw)
In-Reply-To: <1490020425.2614066.917182456.0E56E387@webmail.messagingengine.com>
On the other side, current padding never adds the padding character
unless the string is shorter than the given limit. With the change, it
would add "_" as described "漢_", suggesting there are no other
characters.
Maybe it should be: not add "_", but do skip the not-fitting character.
This would not meet the "constant length" property..
--
Sebastian Gniazdowski
psprint3@fastmail.com
next prev parent reply other threads:[~2017-03-20 16:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 14:33 Sebastian Gniazdowski
2017-03-20 16:00 ` Sebastian Gniazdowski [this message]
2017-03-20 16:43 ` Bart Schaefer
2017-03-21 13:02 Sebastian Gniazdowski
2017-04-02 22:57 ` Bart Schaefer
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=1490025646.2635901.917311768.731A36CF@webmail.messagingengine.com \
--to=psprint3@fastmail.com \
--cc=zsh-workers@zsh.org \
/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).