From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: [PATCH] add build-time option to use unicode9 character widths
Date: Wed, 30 Nov 2016 10:27:37 +0000 [thread overview]
Message-ID: <20161130102737.22c530b9@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAHYJk3T6nVR2ckv2ruDb=YWSHNxQZiSpakYyJEv1L6n7djVq_A@mail.gmail.com>
On Wed, 30 Nov 2016 10:53:16 +0100
Mikael Magnusson <mikachu@gmail.com> wrote:
> Hopefully glibc catches up to the spec sooner rather than later, or
> does a runtime thing. It's kinda useless if only zsh supports it
> anyway, since your terminal needs to also display it correctly.
That's worth pointing out so people don't waste time.
pws
diff --git a/NEWS b/NEWS
index 433703a..403cd61 100644
--- a/NEWS
+++ b/NEWS
@@ -7,6 +7,13 @@ Note also the list of incompatibilities in the README file.
Changes from 5.2 to 5.3
-----------------------
+It is possible to enable character width support for Unicode 9 by
+configuring with `--enable-unicode9'; this compiles in some additional
+tables. At some point this support may move into a module, in which
+case the configure option will be changed to cause the module to be
+permanently loaded. This option is not useful unless your terminal also
+supports Unicode 9.
+
The new word modifier ':P' computes the physical path of the argument.
It is different from the existing ':a' modifier which always resolves
'/before/here/../after' to '/before/after', and differs from the
prev parent reply other threads:[~2016-11-30 10:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20161129080722epcas3p3b988ea1997082b500e96febcab712655@epcas3p3.samsung.com>
2016-11-29 7:42 ` Joshua Rubin
2016-11-29 7:42 ` Joshua Rubin
2016-11-30 10:49 ` Jun T.
2016-11-29 17:21 ` Peter Stephenson
2016-11-29 19:53 ` Bart Schaefer
2016-11-30 9:49 ` Peter Stephenson
2016-11-30 9:53 ` Mikael Magnusson
2016-11-30 10:27 ` 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=20161130102737.22c530b9@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.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).