unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 74383@debbugs.gnu.org
Cc: luangruo@yahoo.com, ba.tahaaziz@gmail.com, eliz@gnu.org
Subject: bug#74383: 29.4; Emacs PGTK crashes on Void Linux
Date: Sun, 17 Nov 2024 12:48:45 +0200	[thread overview]
Message-ID: <44553.8678251737$1731840641@news.gmane.org> (raw)
In-Reply-To: <87jzd2gpd4.fsf@yahoo.com> (Po Lu via's message of "Sun, 17 Nov 2024 17:51:19 +0800")

Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>> Which GTK versions dropped XPM support?
>
> I don't know.  I only learned of this fact this morning myself.
>
>> We should probably reject those versions at configure time, if they
>> lead to Emacs that crashes on startup.
>
> It's not GTK that has deprecated XPM support, but a library it invokes
> to load image files.  From what I've heard, it remains possible to
> configure the library with XPM support.

Is it possible to gracefully crash or disable toolbar support when XPM
support is disabled?

There's gdk_pixbuf_format_is_disabled to check if a format is disabled.[1]

[1] https://docs.gtk.org/gdk-pixbuf/method.PixbufFormat.is_disabled.html





  reply	other threads:[~2024-11-17 10:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-16 12:42 bug#74383: 29.4; Emacs PGTK crashes on Void Linux Taha Aziz Ben Ali
2024-11-16 16:56 ` Eli Zaretskii
2024-11-16 18:01   ` Taha Aziz Ben Ali
2024-11-16 18:42     ` Eli Zaretskii
2024-11-16 20:15       ` Taha Aziz Ben Ali
2024-11-16 20:54         ` Eli Zaretskii
2024-11-16 21:21           ` Taha Aziz Ben Ali
2024-11-17  0:12   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17  6:06     ` Eli Zaretskii
2024-11-17  9:51       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17 10:48         ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-11-17 10:48         ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-17 11:40     ` Taha Aziz Ben Ali
2024-11-17 12:04       ` Eli Zaretskii
2024-11-17 12:23         ` Taha Aziz Ben Ali
2024-11-17 12:48           ` Eli Zaretskii
2024-11-17 13:08             ` Taha Aziz Ben Ali
2024-11-17 13:15               ` Taha Aziz Ben Ali
2024-11-17 13:24                 ` Eli Zaretskii
2024-11-17 13:47                 ` Eli Zaretskii
2024-11-17 14:07                   ` Taha Aziz Ben Ali
2024-11-17 17:34 ` Taha Aziz Ben Ali
2024-11-17 17:40   ` Eli Zaretskii

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='44553.8678251737$1731840641@news.gmane.org' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=74383@debbugs.gnu.org \
    --cc=ba.tahaaziz@gmail.com \
    --cc=bjorn.bidar@thaodan.de \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.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).