unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Artur Malabarba <bruce.connor.am@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: On the masking of undisplayable characters
Date: Tue, 7 Jul 2015 10:32:35 +0100	[thread overview]
Message-ID: <CAAdUY-Lpod21GE54s8TBT70QhouopgUD2u23x26NkoYsJPO_ig@mail.gmail.com> (raw)
In-Reply-To: <83vbdwvga9.fsf@gnu.org>

> It should happen only with quotes, and presumably only in
> documentation-related buffers.  The rationale is that we cannot afford
> showing illegible documentation to users just because their terminal
> is incapable of displaying these important characters.
>
> I suggested to limit this to windows showing *Help* buffers, but it
> was decided to wait until someone complains.

I would be much more confortable if this only turned on by default in
buffers where we _know_ that's ok, such as *help* buffers, info
buffers, and maybe Emacs sources.
What bothers me is that it'll happen on any buffer without
confirmation or notification.

Let's say the user is reading some code designed to read a stream and
do something with quotation marks. Or maybe the user is reading prose
in a context where typography is important.
Usually they'll have a font to display these round quotations, but if
they start emacs without a graphical frame for one reason or another
(or, god forbid, they've misconfigured something) then it would a
problem that they see " when they actually have “ or ”.

Now, those are not very likely scenarios, that's why it bothers me a
little less if it's just quotation marks. But I wanted to make sure
we're aware of this, specially if this feature starts spreading to
other characters.

> Not really: the display engine doesn't examine any of those
> characters, until they are on or very near to the visible portion of
> the buffer.

Yeah, I see how that would be complicated.

I guess I'll just step down from soap box now.



  reply	other threads:[~2015-07-07  9:32 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-06 17:38 On the masking of undisplayable characters bruce.connor.am
2015-07-06 18:16 ` Eli Zaretskii
2015-07-06 19:57   ` Artur Malabarba
2015-07-06 23:07     ` Juri Linkov
2015-07-07  2:44       ` Eli Zaretskii
2015-07-07 14:53         ` Eli Zaretskii
2015-07-07  2:43     ` Eli Zaretskii
2015-07-07  9:32       ` Artur Malabarba [this message]
2015-07-07 12:17         ` Yuri Khan
2015-07-07 12:29           ` Artur Malabarba
2015-07-07 13:14             ` Yuri Khan
2015-07-07 13:23               ` Artur Malabarba
2015-07-20 11:02             ` N. Jackson
2015-07-07 15:51         ` Stefan Monnier

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=CAAdUY-Lpod21GE54s8TBT70QhouopgUD2u23x26NkoYsJPO_ig@mail.gmail.com \
    --to=bruce.connor.am@gmail.com \
    --cc=eliz@gnu.org \
    --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).