From: Bruno Barbier <brubar.cs@gmail.com>
To: Marco Antoniotti <marcoxa@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Waiting for 'compile' to finish
Date: Thu, 09 Jan 2025 23:02:03 +0100 [thread overview]
Message-ID: <6780475d.050a0220.1ffe1.d6ae@mx.google.com> (raw)
In-Reply-To: <CAKmY7cUgTnERgaeD9vDjNWrCuP2X5cJ9NJ+tpWuPxdUqkukMDQ@mail.gmail.com>
Marco Antoniotti <marcoxa@gmail.com> writes:
> Yep. That much I surmised. It does not seem to be mentioned in the Info
> documentation.
Here is a function that compiles and do something when done using
`compilation-exit-message-function'.
(defun my-compile (cmd on-exit)
"Compile using CMD. Return the buffer.
Call ON-EXIT when done."
(let ((buffer (compile cmd)))
(with-current-buffer buffer
(add-function :around (local 'compilation-exit-message-function)
(lambda (old-fun process-status exit-status msg)
(let ((mm (funcall old-fun process-status exit-status msg)))
(funcall on-exit process-status exit-status msg)
mm))))
buffer))
Here is an example about how to use it.
(defun my-compile-echo-result (process-status exit-status msg)
"An ON-EXIT example that just displays OK or Failed."
(message "Compilation: %s" (if (eq 0 exit-status) "OK." "Failed!")))
;; A compilation that succeeds.
(my-compile "sleep 1; echo ok" #'my-compile-echo-result)
;; A compilation that fails.
(my-compile "sleep 1; oops" #'my-compile-echo-result)
Hoping this may help you,
Bruno
> All the best
>
> MA
>
> On Thu, Jan 9, 2025 at 10:23 PM Bruno Barbier <brubar.cs@gmail.com> wrote:
>
>> Marco Antoniotti <marcoxa@gmail.com> writes:
>>
>> > Thanks, I'll check it out. But where is this documented?
>> >
>>
>> It seems that the only documentation is the variable definition itself:
>>
>> C-h v compilation-exit-message-function
>>
>>
>> Bruno
>>
>
>
> --
> Marco Antoniotti
> Somewhere over the Rainbow
next prev parent reply other threads:[~2025-01-09 22:02 UTC|newest]
Thread overview: 13+ 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 [this message]
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
2025-01-09 23:35 ` Stefan Monnier via Users list for the GNU Emacs text editor
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=6780475d.050a0220.1ffe1.d6ae@mx.google.com \
--to=brubar.cs@gmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=marcoxa@gmail.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).