From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: replacing some utf-8 characters on display
Date: Wed, 27 Oct 2021 18:00:42 +0200 [thread overview]
Message-ID: <874k928nkl.fsf@gnus.org> (raw)
In-Reply-To: <87sfwm1n1m.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Wed, 27 Oct 2021 16:53:57 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> I am currently receiving emails with ⚠ which I would like to have
> display a ⚠️ instead in gnus. Just for æsthetic reasons...
>
> Is there some automatic way (some washing treatment) to handle this?
No, but it's trivial to add. You just look at each character and add
the VS-16 after it:
(when (eq (aref char-script-table char) 'symbol)
(insert (string #xfe0f)))
Then you'll get the "emoji" expression (if it exists) from everything
that's a symbol. I think.
However, this may be confusing for some symbols, I think? Not for ⚠,
where it's aesthetic only, but I'm wondering whether there's, like, math
symbols that have the same VS-16 behaviour. (VS-16 means "use the emoji
glyph instead of the symbol glyph".)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-10-27 16:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 15:53 Eric S Fraga
2021-10-27 16:00 ` Lars Ingebrigtsen [this message]
2021-10-27 16:04 ` Eric S Fraga
2021-10-27 16:10 ` Lars Ingebrigtsen
2021-10-27 16:21 ` Eric S Fraga
2021-10-27 16:39 ` Robert Pluim
2021-10-28 22:01 ` Lars Ingebrigtsen
2021-11-03 10:33 ` Robert Pluim
2021-11-04 5:14 ` Lars Ingebrigtsen
2021-11-04 5:38 ` Lars Ingebrigtsen
2021-11-04 5:51 ` Lars Ingebrigtsen
2021-11-04 5:55 ` Lars Ingebrigtsen
2021-11-10 15:12 ` Eric S Fraga
2021-11-10 15:15 ` Eric S Fraga
2021-11-10 15:17 ` Eric S Fraga
2021-11-04 12:26 ` Eric S Fraga
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=874k928nkl.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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.
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 NNTP newsgroup(s).