From: Po Lu <luangruo@yahoo.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master ed84f24a21: Make `signal-process' allow completing over signal names
Date: Tue, 28 Jun 2022 21:35:17 +0800 [thread overview]
Message-ID: <87v8skc3my.fsf@yahoo.com> (raw)
In-Reply-To: <87bkucq5gi.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 28 Jun 2022 15:32:13 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> I don't follow. SIGNUM_BOUND is only defined in sig2str.h, so it won't
> be bound if we use the OS sig2str. (Unless the OS one also defines a
> header that includes that, but I have no idea whether that's the case or
> not.)
The OS sig2str is defined in signal.h. sig2str.h only exists in gnulib.
Further more, gnulib headers regularly override only "parts" of the
system headers, in order to make up for missing (or incorrectly defined)
features. Any .h file in lib/ is included preferentially.
prev parent reply other threads:[~2022-06-28 13:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <165627647702.21409.11158107897633930882@vcs2.savannah.gnu.org>
[not found] ` <20220626204757.57AB1C01685@vcs2.savannah.gnu.org>
2022-06-27 1:20 ` master ed84f24a21: Make `signal-process' allow completing over signal names Po Lu
2022-06-27 6:37 ` Lars Ingebrigtsen
2022-06-27 6:51 ` Po Lu
2022-06-27 6:56 ` Lars Ingebrigtsen
2022-06-27 7:04 ` Po Lu
2022-06-27 7:10 ` Lars Ingebrigtsen
2022-06-27 8:10 ` Po Lu
2022-06-27 8:12 ` Lars Ingebrigtsen
2022-06-27 8:25 ` Po Lu
2022-06-27 8:47 ` Daniel Martín
2022-06-27 10:55 ` Lars Ingebrigtsen
2022-06-27 11:36 ` Eli Zaretskii
2022-06-28 11:23 ` Lars Ingebrigtsen
2022-06-28 13:19 ` Po Lu
2022-06-28 13:25 ` Lars Ingebrigtsen
2022-06-28 13:28 ` Po Lu
2022-06-28 13:32 ` Lars Ingebrigtsen
2022-06-28 13:34 ` Lars Ingebrigtsen
2022-06-28 13:35 ` Po Lu [this message]
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=87v8skc3my.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).