From: Thibault Polge <thibault@thb.lt>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 52018@debbugs.gnu.org
Subject: bug#52018: 28.0.60; Improve documentation for compilation-finish-functions
Date: Sun, 21 Nov 2021 20:08:56 +0100 [thread overview]
Message-ID: <87wnl1gwc7.fsf@thb.lt> (raw)
In-Reply-To: <83sfvpr17k.fsf@gnu.org>
> But this is not entirely accurate, is it?
I've done a quick test, and this seems accurate. As I understand it,
the code you quoted:
> (let ((out-string (format ":%s [%s]" process-status (cdr status)))
> (msg (format "%s %s" mode-name
> (replace-regexp-in-string "\n?$" ""
> (car status)))))
comes from a let block that happens in the context of:
(setq mode-line-process [...]
That is used to, IIUC, decorate the mode line with info about the
compilation result. This setq, and the let it wraps, ends just
before:
(force-mode-line-update)
[...]
(run-hook-with-args 'compilation-finish-functions cur-buffer msg)))
So the msg that compilation-handle-exit receives is passed, unmodified,
to all 'compilation-finish-functions`.
Best regards,
Thibault
next prev parent reply other threads:[~2021-11-21 19:08 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 10:48 bug#52018: 28.0.60; Improve documentation for compilation-finish-functions Thibault Polge
2021-11-21 15:13 ` Eli Zaretskii
2021-11-21 19:08 ` Thibault Polge [this message]
2021-11-21 19:25 ` Eli Zaretskii
2021-11-21 19:44 ` Thibault Polge
2021-11-21 19:53 ` Eli Zaretskii
2021-11-21 20:00 ` Thibault Polge
2021-11-21 20:11 ` Eli Zaretskii
2021-11-21 20:20 ` Thibault Polge
2021-11-21 20:29 ` Eli Zaretskii
2021-11-22 9:12 ` Thibault Polge
2021-11-22 16:56 ` Eli Zaretskii
2021-11-23 9:26 ` Thibault Polge
2021-11-23 12:47 ` Eli Zaretskii
2021-11-24 7:02 ` Lars Ingebrigtsen
2021-11-24 12:40 ` Eli Zaretskii
2021-11-24 16:31 ` Lars Ingebrigtsen
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=87wnl1gwc7.fsf@thb.lt \
--to=thibault@thb.lt \
--cc=52018@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.