public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Po Lu <luangruo@yahoo.com>,
	GNU C Library development <libc-alpha@sourceware.org>
Subject: Re: Hook for `_exit'
Date: Fri, 5 Aug 2022 20:20:25 +0100	[thread overview]
Message-ID: <Yu1teY7bn9lUVNkp@arm.com> (raw)
In-Reply-To: <bf177b4c-74b3-56df-bc01-4d2cc080e8f4@cs.ucla.edu>

The 08/05/2022 10:43, Paul Eggert wrote:
> On 8/5/22 03:52, Po Lu via Libc-alpha wrote:
> > the GTK developers
> > are unwilling to provide proper hooks (or even to use exit) instead.
> 
> Matthias suggested in <https://gitlab.gnome.org/GNOME/gtk/-/issues/4514>
> that Emacs could use a g_message hook and parse the message to determine
> that GTK is about to _exit. Although a horrible hack, I've seen worse hacks
> in Emacs.

btw can't emacs interpose _exit?

(and use something else when it really wants to exit)

  reply	other threads:[~2022-08-05 19:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87les389c6.fsf.ref@yahoo.com>
2022-08-05  6:59 ` Po Lu
2022-08-05  8:22   ` Florian Weimer
2022-08-05  8:35     ` Po Lu
2022-08-05  8:38       ` Florian Weimer
2022-08-05  8:41         ` Po Lu
2022-08-05  8:47           ` Florian Weimer
2022-08-05  8:59             ` Po Lu
2022-08-05  9:02               ` Florian Weimer
2022-08-05  9:55                 ` Cyril Hrubis
2022-08-05 10:52                 ` Po Lu
2022-08-05 17:43                   ` Paul Eggert
2022-08-05 19:20                     ` Szabolcs Nagy [this message]
2022-08-05 20:11                       ` Paul Eggert
2022-08-05 22:41                         ` Adhemerval Zanella
2022-08-06  1:37                     ` Po Lu
2022-08-06  8:23                       ` Paul Eggert
2022-08-05 19:17     ` Rich Felker

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=Yu1teY7bn9lUVNkp@arm.com \
    --to=szabolcs.nagy@arm.com \
    --cc=eggert@cs.ucla.edu \
    --cc=libc-alpha@sourceware.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.
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).