From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 28785@debbugs.gnu.org
Subject: bug#28785: 27.0.50; Wishlist: There should be a mode for .netrc and .authinfo
Date: Sat, 21 Sep 2019 12:19:41 +0300 [thread overview]
Message-ID: <83o8zeqa4y.fsf@gnu.org> (raw)
In-Reply-To: <871rwa10wk.fsf@gnus.org> (message from Lars Ingebrigtsen on Sat, 21 Sep 2019 10:58:19 +0200)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Sat, 21 Sep 2019 10:58:19 +0200
>
> I thought I'd take a what at this, but if I remember correctly, the
> consensus on emacs-devel was that this mode should just call
> prettify-symbols-mode.
FWIW, I'd prefer we didn't proliferate prettify-symbols-mode more than
it is already, because I hope it will go away some time soon, to be
replaced by true ligature support.
> But looking at that mode, it seems like it doesn't really work on
> regexps, and doesn't allow translating to strings? It just takes
> literal strings and displays is as a char?
Yes, it's pretty limited. What's more, it uses infrastructure (static
character composition) that was a temporary hack way back, when
automatic composition was not yet available, and we should at some
point deprecate and remove it.
> Does anybody remember whether this really was the conclusion, or whether
> there's another framework for hiding stuff that should be used?
I suggest to only consider the second part of that ;-)
In general, you can hide stuff with display properties, and I'm unsure
what additional framework you'd need for that.
Thanks.
prev parent reply other threads:[~2019-09-21 9:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 11:45 bug#28785: 27.0.50; Wishlist: There should be a mode for .netrc and .authinfo Lars Ingebrigtsen
2017-12-21 15:02 ` Ted Zlatanov
2017-12-21 15:10 ` Lars Ingebrigtsen
2018-04-13 23:19 ` Lars Ingebrigtsen
2019-09-21 8:58 ` Lars Ingebrigtsen
2019-09-21 9:10 ` Lars Ingebrigtsen
2019-09-21 10:06 ` Lars Ingebrigtsen
2019-09-21 9:19 ` Eli Zaretskii [this message]
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=83o8zeqa4y.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=28785@debbugs.gnu.org \
--cc=larsi@gnus.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.