all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: 22.2.50; Display of "zero width no-break space" (U+FEFF)
Date: Wed, 23 Apr 2008 01:14:29 -0400	[thread overview]
Message-ID: <8763u9kv9m.fsf@stupidchicken.com> (raw)
In-Reply-To: <87tzhu7qyy.fsf@jurta.org> (Juri Linkov's message of "Tue, 22 Apr 2008 01:33:09 +0300")

Juri Linkov <juri@jurta.org> writes:

>>>> This is the same character as BOM.  But since it is *ZERO-WIDTH*
>>>> NO-BREAK SPACE, it seems it shouldn't be displayed at all in view mode.
>>>> But it edit mode, it would be preferable to have some indication
>>>> about the presence of this character in the buffer.
>>
>> If "view mode" is meant to be more general than the minor mode
>> `view-mode', I agree.  E.g. in Gnus article buffer (a read-only buffer
>> where articles are displayed), `nobreak-char-display' is set to nil
>> whereas when composing or replying, Emacs' default is used.
>
> We definitely should highlight ZERO-WIDTH NO-BREAK SPACE in
> whitespace-mode, but for editing modes I'm not so sure.

By default, Emacs should highlight ZERO-WIDTH NO-BREAK SPACE.  If
individual major modes, like Gnus buffers, want to hide this character,
that's up to them; we don't have to worry about it.  It's just like how
Emacs ordinarily displays page breaks as ^L, whereas the Gnus article
buffer has special code to split articles into pages.




  reply	other threads:[~2008-04-23  5:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-06 20:53 22.2.50; Display of "zero width no-break space" (U+FEFF) Reiner Steib
2008-04-20 10:35 ` Reiner Steib
2008-04-20 23:57   ` Juri Linkov
2008-04-21  3:09     ` Eli Zaretskii
2008-04-21 11:51       ` Reiner Steib
2008-04-21 22:33         ` Juri Linkov
2008-04-23  5:14           ` Chong Yidong [this message]
2012-04-26  8:33 ` bug#121: " Chong Yidong

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=8763u9kv9m.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@jurta.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.