From: Eli Zaretskii <eliz@gnu.org>
To: David McCracken <davidm@ixont.com>
Cc: 60669@debbugs.gnu.org
Subject: bug#60669: Linux Emacs 27.1 custom toolbar icons
Date: Mon, 09 Jan 2023 05:32:58 +0200 [thread overview]
Message-ID: <83eds4pel1.fsf@gnu.org> (raw)
In-Reply-To: <998e8e01-2c89-da4b-9c36-83b987af3bdf@ixont.com> (message from David McCracken on Sun, 8 Jan 2023 13:01:26 -0800)
> Date: Sun, 8 Jan 2023 13:01:26 -0800
> From: David McCracken <davidm@ixont.com>
>
> The Emacs 27.1 provided (apt-get install) by Ubuntu 22.04 reduces
> support for custom toolbar icons. It only works with B/W pbm files and
> only if located in /usr/share/emacs/27.1/etc/images and only if there
> isn't an xpm file with the same base name. i.e. name.pbm works but not
> if there is a name.xpm in the directory. If these conditions are not met
> nothing is displayed.
>
> This does not seem to be baked into Emacs 27.1 because these
> restrictions don't exist in Windows Emacs 27.1. They are also not
> inherent in Linux because they don't exist in Linux Emacs 26.1.
>
> There are two serious problems with these seemingly unnecessary changes.
> B/W icons reduce not just the aesthetic quality but also subtle visual
> clues that help an icon convey its meaning. Accepting only icons in the
> version-numbered installation directory means that custom icons are
> wiped out by upgrading Emacs.
>
> The installer program I provide with my Emacs library stores its (xpm)
> icons in ~/icons (a directory created by my installer). My library
> accesses these by e.g.
> (tool-bar-add-item "~/icons/lxa-pin"
> Linux Emacs 27.1 is the only version in which this does not work. To
> test whether it does not like that the directory is relatively insecure,
> I tried moving my icons to /usr/local but they were still ignored. In
> all other versions, adding the xpm extension to the reference causes it
> to fail but I tested this anyway and it accomplished nothing.
Can you please show a reproducible recipe, starting from "emacs -Q",
that exhibits the problem you are describing? I don't think I
understand what exactly doesn't work in your case.
Also, please use "M-x report-emacs-bug" to post the details, as that
command collects important details about the Emacs build configuration
that make investigation easier.
Thanks.
next prev parent reply other threads:[~2023-01-09 3:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-08 21:01 bug#60669: Linux Emacs 27.1 custom toolbar icons David McCracken
2023-01-09 3:32 ` Eli Zaretskii [this message]
2023-09-03 9:41 ` Stefan Kangas
2023-09-08 4:07 ` David McCracken
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=83eds4pel1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60669@debbugs.gnu.org \
--cc=davidm@ixont.com \
/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).