From: Kenichi Handa <handa@m17n.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: eliz@gnu.org, ulm@gentoo.org, emacs-devel@gnu.org
Subject: Re: Display of characters #xa0 and #xad in unibyte buffers
Date: Tue, 29 Sep 2009 16:52:17 +0900 [thread overview]
Message-ID: <tl7ab0erxvy.fsf@m17n.org> (raw)
In-Reply-To: <jwvske65tow.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Mon, 28 Sep 2009 23:15:43 -0400)
In article <jwvske65tow.fsf-monnier+emacs@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca> writes:
>>> I think in such a case, the bug is to use
>>> unibyte-display-via-language-environment and expect it to affect more
>>> than the display.
> > Then, how about adding this statement in the docstring (or to info)?
> > "It doesn't affect how each character is interpreted."
> Maybe we could try to make it more obvious that it only affects display
> and nothing else. Then again, we should also make it more clear that
> you should stay away from this feature.
I'm not good at writing that kind of document. Could
someone please install a proper docstring/info-text?
---
Kenichi Handa
handa@m17n.org
next prev parent reply other threads:[~2009-09-29 7:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-24 15:06 Display of characters #xa0 and #xad in unibyte buffers Ulrich Mueller
2009-09-25 8:31 ` Eli Zaretskii
2009-09-25 9:00 ` Ulrich Mueller
2009-09-25 9:14 ` Eli Zaretskii
2009-09-28 1:10 ` Kenichi Handa
2009-09-28 6:43 ` Eli Zaretskii
2009-09-28 11:24 ` Kenichi Handa
2009-09-28 14:10 ` Eli Zaretskii
2009-09-28 22:38 ` Stefan Monnier
2009-09-29 1:05 ` Kenichi Handa
2009-09-29 1:35 ` Stefan Monnier
2009-09-29 2:37 ` Kenichi Handa
2009-09-29 3:15 ` Stefan Monnier
2009-09-29 7:52 ` Kenichi Handa [this message]
[not found] ` <831vljpm0v.fsf@gnu.org>
2009-10-05 0:49 ` Kenichi Handa
2009-09-25 9:38 ` Stephen J. Turnbull
2009-09-25 14:09 ` Stefan Monnier
2009-09-26 8:26 ` Ulrich Mueller
2009-09-25 9:44 ` Andreas Schwab
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=tl7ab0erxvy.fsf@m17n.org \
--to=handa@m17n.org \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=ulm@gentoo.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).