From: "João Távora" <joaotavora@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 50989@debbugs.gnu.org, Augusto Stoffel <arstoffel@gmail.com>
Subject: bug#50989: 28.0.60; nobreak-char-display in Eldoc buffers
Date: Sun, 3 Oct 2021 12:12:23 +0100 [thread overview]
Message-ID: <CALDnm50Ov0uG43i1Wfh8875RnMYnMDr6OG1jTuFgRPxcHc=Psg@mail.gmail.com> (raw)
In-Reply-To: <83y27a8iyq.fsf@gnu.org>
On Sun, Oct 3, 2021 at 12:07 PM Eli Zaretskii <eliz@gnu.org> wrote:
> IMNSHO, this doesn't make much sense. That face exists for a reason:
> to signal to the users that some innocently-looking characters aren't
> what they look like.
Eldoc's display facilities are only for displaying. Sure, you may want
to copy text away from there, but I'd say that's rare. So it wouldn't
be a problem
in practice, unless I'm missing something
> Why does the server return these NBSP characters? Would it make sense
> to automatically convert them to spaces on input?
That's also sweeping it under the rug. But I don't object either. Augusto, if
you agree, match a patch to Eglot (this is where I presume the "input"
Eli refers
to lives). Of course the real input is the server, but I'd rather not
go there, since
there are so many and all are out of our control.
João
next prev parent reply other threads:[~2021-10-03 11:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-03 10:02 bug#50989: 28.0.60; nobreak-char-display in Eldoc buffers Augusto Stoffel
2021-10-03 10:34 ` João Távora
2021-10-03 11:07 ` Eli Zaretskii
2021-10-03 11:12 ` João Távora [this message]
2021-10-03 11:25 ` Eli Zaretskii
2021-10-03 11:39 ` Augusto Stoffel
2021-10-05 9:13 ` Lars Ingebrigtsen
2021-10-05 21:16 ` Richard Stallman
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='CALDnm50Ov0uG43i1Wfh8875RnMYnMDr6OG1jTuFgRPxcHc=Psg@mail.gmail.com' \
--to=joaotavora@gmail.com \
--cc=50989@debbugs.gnu.org \
--cc=arstoffel@gmail.com \
--cc=eliz@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).