From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: Waiting for 'compile' to finish
Date: Fri, 10 Jan 2025 09:06:35 -0500 [thread overview]
Message-ID: <jwvzfjyahuk.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: 87a5bzc961.fsf@neko.mail-host-address-is-not-set
> but I found even better solution in my .emacs using
> set-process-sentinel, something like this:
>
> (set-process-sentinel
> (get-buffer-process (get-buffer eepitch-buffer-name))
> (lambda (_process event)
> (when (equal "finished\n" event)
> (run-with-idle-timer 1 nil after))))
In the more general case, the process might already have a sentinel set
so the above could have undesirable side effects. But you can use
`add-function` to avoid the problem:
(add-function
:before
(process-sentinel
(get-buffer-process (get-buffer eepitch-buffer-name)))
(lambda (_process event)
(when (equal "finished\n" event)
(run-with-idle-timer 1 nil after))))
Adding elements (IOW, "multiplexing" the sentinel) to a process sentinel
was actually the problem that spurred the development of `nadvice.el`.
🙂
Stefan
next prev parent reply other threads:[~2025-01-10 14:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 19:44 Waiting for 'compile' to finish Marco Antoniotti
2025-01-09 19:50 ` Tomas Hlavaty
2025-01-09 20:00 ` Marco Antoniotti
2025-01-09 20:18 ` Bruno Barbier
2025-01-09 21:05 ` Marco Antoniotti
2025-01-09 21:23 ` Bruno Barbier
2025-01-09 21:25 ` Marco Antoniotti
2025-01-09 22:02 ` Bruno Barbier
2025-01-09 21:36 ` Tomas Hlavaty
2025-01-09 21:38 ` Marco Antoniotti
2025-01-10 9:25 ` Tomas Hlavaty
2025-01-10 14:06 ` Stefan Monnier via Users list for the GNU Emacs text editor [this message]
2025-01-09 23:35 ` Stefan Monnier via Users list for the GNU Emacs text editor
2025-01-10 15:44 ` Óscar Fuentes
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=jwvzfjyahuk.fsf-monnier+emacs@gnu.org \
--to=help-gnu-emacs@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).