--- Begin Message ---
Subject: |
Replace XPM icons with Unicode codepoints in customize/widgets |
Date: |
Thu, 11 Mar 2021 10:51:19 -0600 |
Severity: wishlist
In M-x customize, we use the etc/images/{un,}checked.xpm and other
icons. These images do not scale when you increase the font, and (this
is subjective but) generally don't look too good.
I think we could get better result if we used Unicode characters like:
- ☑ checked
- ☐ unchecked
- ▼ or ▾ down triangle
- ▶ or ▸ right triangle
I'm less sure about the look of these but they do exist:
- ⬤ or ◉ or 🔘 radio button selected (the last one was added to Unicode
in 2015 and gives the hex square here)
- ◯ radio button unselected
Obviously how these look depends on the fonts you have installed. On my
machine, the "Fira Code" font is used, which makes them look very good.
(They also obviously scale when increasing the font size.)
Perhaps we could prefer Unicode icons if they are available, and fall
back on icons if not. It seems like we can use `char-displayable-p' to
see if there is any font that can display that codepoint.
If we don't think that will produce consistently improved results, we
could also just add a new option to use Unicode characters.
Thoughts?
--- End Message ---
--- Begin Message ---
Subject: |
Re: bug#47074: Replace XPM icons with Unicode codepoints in customize/widgets |
Date: |
Sat, 3 Apr 2021 23:28:35 +0100 |
On Sat, Apr 03, 2021 at 03:06:57PM -0500, Stefan Kangas wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Mon, 15 Mar 2021 21:34:24 +0000
> >> From: Alan Third <alan@idiocy.org>
> >> Cc: stefan@marxist.se, 47074@debbugs.gnu.org
> >>
> >> Here's my final patch, then. Again Stefan's patch is required first.
> >
> > Thanks. As discussed elsewhere, Stefan's patch will have to be
> > slightly reworked to allow Emacs without SVG support to display
> > equivalent images of other formats.
>
> I have now pushed it to master. The XPM files are now used when
> configuring --without-rsvg, and SVG is used otherwise (the default
> case).
>
> Eli insisted on keeping the old file names, so the file names in your
> patch will need to be changed accordingly.
I've pushed a change up, so hopefully it should all Just Work now.
Thanks!
--
Alan Third
--- End Message ---