zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <psprint@zdharma.org>
To: zsh-workers@zsh.org, Peter Stephenson <p.stephenson@samsung.com>
Subject: Re: Cannot paste unicode <0221>, <0234> - <024f>
Date: Fri, 28 Apr 2017 15:54:23 +0200	[thread overview]
Message-ID: <etPan.5903498f.140e0f76.15fbc@MacMini.local> (raw)
In-Reply-To: <20170428141650.7ed174d6@pwslap01u.europe.root.pri>

On 28 April 2017 at 15:17:40, Peter Stephenson (p.stephenson@samsung.com) wrote:
> Probably worth checking if BROKEN_WCWIDTH is already defined in config.h
> and if not what happens if you define it. It has no effect unless
> one of __STDC_ISO_10646__ or __APPLE__ is also defined.

Tried defining it with the wcwidth hack and without – no change. System is OS X so there is __APPLE__.

> An other option is --enable-unicode9, but you'll need the appropriate
> header and library support for that to work.

I've installed iconv, it got somewhat detected:
checking iconv.h usability... yes
checking iconv.h presence... yes
checking for iconv.h... yes
...
checking for iconv... no
checking for iconv in -liconv... no
checking for libiconv in -liconv... yes
checking for iconv declaration...

-liconv was in configure status, and zsh binary is actually linked with it. However, no luck with pasting "ȮȯȰȱȲȳȴȵȶȷȸȹ", result is the same, also with insert-unicode-char

> You might want to confirm also if it actually is wcwidth() rather than
> iswprint() by hacking zle_refresh.c e.g. the following (untested). This
> might be a plausible patch, actually --- if iswprint() succeeds,
> presumably the printing width actually is positive (combining characters
> are handled as a special case afterwards).

Tried the patch, no luck, result is the same

--
Sebastian Gniazdowski
psprint /at/ zdharma.org


  reply	other threads:[~2017-04-28 13:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170428111102epcas3p1cc3d86dc54fdafd8cd0e613bbaeba69b@epcas3p1.samsung.com>
2017-04-28 10:55 ` Sebastian Gniazdowski
2017-04-28 11:44   ` Peter Stephenson
2017-04-28 12:11     ` Sebastian Gniazdowski
2017-04-28 13:16       ` Peter Stephenson
2017-04-28 13:54         ` Sebastian Gniazdowski [this message]
2017-04-28 14:10           ` Peter Stephenson
2017-04-28 14:41           ` Peter Stephenson
2017-04-28 15:27             ` Sebastian Gniazdowski
2017-04-28 15:43               ` Peter Stephenson
2017-04-28 16:11                 ` Sebastian Gniazdowski
2017-04-29  6:39             ` Sebastian Gniazdowski
2017-05-01  2:53               ` Jun T.
2017-05-01 15:52                 ` Jun T.
2017-05-02 13:15                   ` Peter Stephenson
2017-05-06 15:58                   ` Sebastian Gniazdowski
2017-05-06 18:11                     ` Bart Schaefer
2017-05-07  9:50                       ` Sebastian Gniazdowski
2017-05-08  2:44                         ` Daniel Shahaf
2017-05-08  4:04                           ` Gmail patch extraction (was: Cannot paste unicode <0221>, <0234> - <024f>) Sebastian Gniazdowski
2017-05-08  4:33                             ` Sebastian Gniazdowski
2017-05-08 11:07                               ` Daniel Shahaf
2017-05-06 18:39                     ` Cannot paste unicode <0221>, <0234> - <024f> Daniel Shahaf
2017-05-07 10:13                   ` Sebastian Gniazdowski
2017-05-10 11:29                   ` Jun T.
2017-05-12  7:50                     ` Sebastian Gniazdowski

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=etPan.5903498f.140e0f76.15fbc@MacMini.local \
    --to=psprint@zdharma.org \
    --cc=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).