unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dmitry@gutov.dev>
To: Eli Zaretskii <eliz@gnu.org>
Cc: itaemu@gmail.com, casouri@gmail.com, 64420@debbugs.gnu.org
Subject: bug#64420: string-width of … is 2 in CJK environments
Date: Sat, 12 Aug 2023 19:40:01 +0300	[thread overview]
Message-ID: <875f847b-b805-ce63-0d8a-1bae68df0119@gutov.dev> (raw)
In-Reply-To: <83pm3sg675.fsf@gnu.org>

On 12/08/2023 08:50, Eli Zaretskii wrote:
>> Date: Sat, 12 Aug 2023 02:52:29 +0300
>> Cc:itaemu@gmail.com,casouri@gmail.com,64420@debbugs.gnu.org
>> From: Dmitry Gutov<dmitry@gutov.dev>
>>
>> On 05/08/2023 18:01, Eli Zaretskii wrote:
>>> OK, this is now installed on master.  We have a new user option named
>>> cjk-ambiguous-chars-are-wide; its default is t, but if set to nil, the
>>> characters proclaimed by Unicode as "ambiguous" will have char-width
>>> of 1, not 2.  Note that this option should be set either via 'setopt'
>>> or the Customize interface, not via 'setq'.
>>>
>>> Let me know how well this works for you.
>> Seems to work fine, thank you.
>>
>> With the caveat that, in the terminal, if I switch to Chinese-BIG5 and
>> visit a file with ambiguous characters like … (which triggers some bugs
>> with display and navigation around those chars), (setopt
>> cjk-ambiguous-chars-are-wide nil) doesn't fix those bugs -- I have to
>> kill and re-visit the buffer for them to go away. But maybe that's expected.
> Does "M-x redraw-display RET" solve the problem after setting the
> variable?

Looks like it does, yes.





  reply	other threads:[~2023-08-12 16:40 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-02 12:57 bug#64420: string-width of … is 2 in CJK environments Dmitry Gutov
2023-07-02 13:10 ` Eli Zaretskii
2023-07-02 13:20   ` Dmitry Gutov
2023-07-02 13:43     ` Eli Zaretskii
2023-07-07  2:13       ` Dmitry Gutov
2023-07-07  6:29         ` Eli Zaretskii
2023-07-11  2:13           ` Dmitry Gutov
2023-07-11 11:41             ` Eli Zaretskii
2023-07-11  2:23       ` Dmitry Gutov
2023-07-11 11:48         ` Eli Zaretskii
2023-07-11 18:13           ` Dmitry Gutov
2023-07-11 18:45             ` Eli Zaretskii
2023-07-12  1:17               ` Dmitry Gutov
2023-07-12 19:54                 ` Dmitry Gutov
2023-07-12 21:11                 ` Yuan Fu
2023-07-13  5:23                   ` Eli Zaretskii
2023-07-27  1:52                     ` Dmitry Gutov
2023-07-14  4:45 ` SUNG TAE KIM
2023-07-14  6:58   ` Eli Zaretskii
2023-07-16 11:51     ` Eli Zaretskii
2023-07-14  9:21 ` SUNG TAE KIM
2023-07-14 11:04   ` Eli Zaretskii
2023-07-14 20:11     ` Yuan Fu
2023-07-16 16:59 ` SUNG TAE KIM
2023-07-16 17:15   ` Eli Zaretskii
2023-08-05 15:01     ` Eli Zaretskii
2023-08-10 21:58       ` Yuan Fu
2023-08-11  5:53         ` Eli Zaretskii
2023-08-11 18:07           ` Yuan Fu
2023-08-11 18:36             ` Eli Zaretskii
2023-08-12 20:18               ` Yuan Fu
2023-08-11 22:34             ` Dmitry Gutov
2023-08-13  0:22             ` Dmitry Gutov
2023-08-13  5:24               ` Eli Zaretskii
2023-08-13 10:48                 ` Dmitry Gutov
2023-08-13 12:01                   ` Eli Zaretskii
2023-08-13 12:53                     ` Dmitry Gutov
2023-08-11 23:52       ` Dmitry Gutov
2023-08-12  5:50         ` Eli Zaretskii
2023-08-12 16:40           ` Dmitry Gutov [this message]
2023-08-12 17:09             ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875f847b-b805-ce63-0d8a-1bae68df0119@gutov.dev \
    --to=dmitry@gutov.dev \
    --cc=64420@debbugs.gnu.org \
    --cc=casouri@gmail.com \
    --cc=eliz@gnu.org \
    --cc=itaemu@gmail.com \
    /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.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).