From: PJ Weisberg <pj@irregularexpressions.net>
To: help-gnu-emacs <Help-gnu-emacs@gnu.org>
Subject: Re: Someting with Emacs visual-line-mode
Date: Tue, 14 Sep 2010 00:09:03 -0700 [thread overview]
Message-ID: <AANLkTi=1oWxjOS=RSmBnNgKwyO=YTuR5QGKHdkdMU05h@mail.gmail.com> (raw)
In-Reply-To: <AANLkTinF-1MdtOAPM1C3SwEWpp_M_2pCSrK6K_5bGRMR@mail.gmail.com>
On Mon, Sep 13, 2010 at 5:46 PM, suvayu ali <fatkasuvayu+linux@gmail.com> wrote:
> On 13 September 2010 17:43, Lennart Borgman <lennart.borgman@gmail.com> wrote:
>> I do not think he wanted visual line mode to be turned off. Why do you
>> say so? FanQing said the line should break, but that it should break
>> at the last Chinese character before the window boundary..
>
> Isn't that the same behaviour as `truncate-lines' set to `nil'?
The behavior you get with truncate-lines set to nil, word-wrap set to
nil, and visual-line-mode set to t is what I think he's looking for
with respect to Chinese characters.
What he's really asking for is for Chinese characters to not "stick
together" like English (etc.) characters do when word-wrap is on.
That would take me by surprise if I had embedded a few Chinese
characters into some English text I was writing and Emacs broke the
line between them, because I'm not used to seeing words that are
"breakable" but not normally separated by a space. I don't know what
the best way would be to handle that I'm sure there are different
rules for different languages that I don't even know about, and all
word-wrap does not is look for the last tab or space.
next prev parent reply other threads:[~2010-09-14 7:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-13 2:22 Someting with Emacs visual-line-mode fanq
2010-09-13 15:54 ` Tim Visher
2010-09-13 20:58 ` Lennart Borgman
2010-09-14 0:36 ` PJ Weisberg
2010-09-14 0:43 ` Lennart Borgman
2010-09-14 0:46 ` suvayu ali
2010-09-14 7:09 ` PJ Weisberg [this message]
2010-09-14 9:16 ` Lennart Borgman
2010-09-14 10:18 ` suvayu ali
2010-09-15 0:06 ` PJ Weisberg
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='AANLkTi=1oWxjOS=RSmBnNgKwyO=YTuR5QGKHdkdMU05h@mail.gmail.com' \
--to=pj@irregularexpressions.net \
--cc=Help-gnu-emacs@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.
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).