unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David McCracken <davidm@ixont.com>
Cc: 71162@debbugs.gnu.org
Subject: bug#71162: bug-gnu-emacs@gnu.org
Date: Sun, 26 May 2024 07:44:21 +0300	[thread overview]
Message-ID: <86jzjhxjve.fsf@gnu.org> (raw)
In-Reply-To: <1ced3036-74eb-40b5-9aa7-950f4cf5ed4b@ixont.com> (message from David McCracken on Sat, 25 May 2024 12:08:33 -0700)

> Date: Sat, 25 May 2024 12:08:33 -0700
> Cc: 71162@debbugs.gnu.org
> From: David McCracken <davidm@ixont.com>
> 
> I use Gimp under Windows to make my icons and they all work in 
> Linux-Emacs 26.1. When I open lxa-next.xpm in Linux-Emacs 26.3 (in 
> Ubuntu-Mate 20.54) the icon is rendered correctly. Linux-Emacs 27.1 (in 
> Ubuntu-Mate 22.04) shows it as a blank box. All systems correctly show 
> my icons in the GUI. I edited lxa-next.xpm as text, completely removing 
> the Windows directory, which isn't proper C code because it doesn't name 
> the variable being defined. Nevertheless, the newer Linux computer's GUI 
> does render it although with less saturated colors. When I include a 
> variable name, "something" or "*/~/icons/lxa-next.xpm", the system 
> renders it as designed. However, Emacs still shows it blank. I tried all 
> of these variations in the 27.1/etc/images directory and Emacs showed 
> them all blank. This did not change with emacs -q so the problem is not 
> caused by my .emacs. The problem also doesn't seem to be caused by 
> Ubuntu-Mate because it renders my icons correctly.

Sorry, I don't understand.  If you do the following on Ubuntu with
Emacs 27.1:

  emacs -Q
  C-x C-f ~/icons/lxa-next.xpm RET

does Emacs 27.1 on Ubuntu display the image, or does it display an
empty box?  If the latter, the problem is that Emacs 27.1 on Ubuntu
that you have installed is not capable of showing XPM images
correctly.  IOW, in that case the problem is not related to the tool
bar, it is related to the general inability of displaying XPM images
in that version of Emacs.





  reply	other threads:[~2024-05-26  4:44 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-24  4:08 bug#71162: bug-gnu-emacs@gnu.org David McCracken
2024-05-24  6:15 ` Eli Zaretskii
     [not found]   ` <9002e131-3466-4a73-a88c-bad260e5b886@ixont.com>
2024-05-25  6:09     ` Eli Zaretskii
2024-05-25 19:08       ` David McCracken
2024-05-26  4:44         ` Eli Zaretskii [this message]
2024-05-25 20:04   ` David McCracken
2024-05-27  4:16   ` David McCracken
2024-05-27 11:20     ` bug#71162: In Linux Emacs 27.1 rejects custom toolbar icons Eli Zaretskii
2024-05-25 10:42 ` bug#71162: bug-gnu-emacs@gnu.org Benjamin Riefenstahl
2024-05-26 20:54 ` bug#71162: In Linux Emacs 27.1 rejects custom toolbar icons David McCracken
2024-05-28  3:56 ` bug#71162: Linux-Emacs > 26 icons 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=86jzjhxjve.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=71162@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).