From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Word wrap for non-whitespace-seperated language
Date: Thu, 05 Mar 2020 06:42:20 +0200 [thread overview]
Message-ID: <835zfjwgyb.fsf@gnu.org> (raw)
In-Reply-To: <9737C398-80FC-4377-91BA-C0891BD5A0F5@gmail.com> (message from Yuan Fu on Wed, 4 Mar 2020 15:34:45 -0500)
> From: Yuan Fu <casouri@gmail.com>
> Date: Wed, 4 Mar 2020 15:34:45 -0500
> Cc: emacs-devel@gnu.org
>
> > You are asking about word wrap? It's part of the basic layout code in
> > the display engine, search xdisp.c for WORD_WRAP.
>
> Thanks, that’s what I meant. Seems to me that simply changing IT_DISPLAYING_WHITESPACE won’t give what I want, since I want the engine to wrap _anywhere_ between Chinese/Japanes/etc characters. Use fill.el and wrap with overlay might be a more tractable approach.
AFAIK "anywhere" is not really correct, because kinsoku rules mandate
that some characters cannot appear at the beginning or end of a line.
I do agree that changing IT_DISPLAYING_WHITESPACE is not the right
approach for this, because it would make redisplay too slow. We need
a smarter algorithm.
next prev parent reply other threads:[~2020-03-05 4:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-04 18:39 Word wrap for non-whitespace-seperated language Yuan Fu
2020-03-04 18:44 ` Eli Zaretskii
2020-03-04 18:51 ` Yuan Fu
2020-03-04 19:16 ` Eli Zaretskii
2020-03-04 20:34 ` Yuan Fu
2020-03-05 4:42 ` Eli Zaretskii [this message]
2020-03-05 22:33 ` Yuan Fu
2020-03-05 22:46 ` Drew Adams
2020-03-05 22:50 ` Yuan Fu
2020-03-06 2:18 ` Yuan Fu
2020-03-07 4:23 ` Richard Stallman
2020-03-07 5:04 ` Yuan Fu
2020-03-07 8:19 ` Eli Zaretskii
2020-03-07 17:30 ` Yuan Fu
2020-03-09 2:52 ` Richard Stallman
2020-03-08 6:16 ` Richard Stallman
2020-03-08 15:04 ` Yuan Fu
2020-03-09 2:50 ` Richard Stallman
2020-03-09 15:44 ` Yuan Fu
2020-03-09 17:20 ` Eli Zaretskii
2020-03-09 20:11 ` Yuan Fu
2020-03-07 8:22 ` Eli Zaretskii
2020-03-07 8:40 ` Lars Ingebrigtsen
2020-03-07 10:50 ` 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=835zfjwgyb.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=casouri@gmail.com \
--cc=emacs-devel@gnu.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.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).