From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 63896@debbugs.gnu.org
Subject: bug#63896: [PATCH] Support annotating and sorting the project list during completion
Date: Wed, 28 Jun 2023 14:45:12 +0300 [thread overview]
Message-ID: <83o7kzvmif.fsf@gnu.org> (raw)
In-Reply-To: <ierv8f8zlzl.fsf@janestreet.com> (message from Spencer Baugh on Tue, 27 Jun 2023 16:30:38 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: 63896@debbugs.gnu.org
> Date: Tue, 27 Jun 2023 16:30:38 -0400
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> +(defvar compilation-exit-status nil
> + "The `process-exit-status' of the compilation process, or nil if not exited yet.")
This should clarify that this is the exit status of the _last_
compilation in this buffer. It should also say that the variable is
always buffer-local. I'd also add a reference to
compilation-process-status, because the value of nil is not
informative enough unless one looks at that other variable.
> +(defvar compilation-process-status nil
> + "The latest `process-status' of the compilation process.")
Likewise here, about the buffer-local part.
I think these variables warrant to be called out in NEWS.
next prev parent reply other threads:[~2023-06-28 11:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 21:20 bug#63896: [PATCH] Support annotating and sorting the project list during completion Spencer Baugh
2023-06-05 11:23 ` Eli Zaretskii
2023-06-13 21:19 ` Spencer Baugh
2023-06-14 12:12 ` Eli Zaretskii
2023-06-15 19:04 ` Spencer Baugh
2023-06-16 5:43 ` Eli Zaretskii
2023-06-16 14:26 ` Spencer Baugh
2023-06-16 15:23 ` Eli Zaretskii
2023-06-27 20:30 ` Spencer Baugh
2023-06-28 11:45 ` Eli Zaretskii [this message]
2023-08-24 1:54 ` Dmitry Gutov
2023-08-24 5:29 ` Eli Zaretskii
2023-08-24 13:08 ` Dmitry Gutov
2023-08-24 14:39 ` Eli Zaretskii
2023-08-24 1:47 ` Dmitry Gutov
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=83o7kzvmif.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63896@debbugs.gnu.org \
--cc=sbaugh@janestreet.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 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.