From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Daniel Martín" <mardani29@yahoo.es>
Cc: Po Lu <luangruo@yahoo.com>, emacs-devel@gnu.org
Subject: Re: master ed84f24a21: Make `signal-process' allow completing over signal names
Date: Mon, 27 Jun 2022 12:55:21 +0200 [thread overview]
Message-ID: <87ilomwf3a.fsf@gnus.org> (raw)
In-Reply-To: <m1pmiu8pd8.fsf@yahoo.es> ("Daniel Martín"'s message of "Mon, 27 Jun 2022 10:47:15 +0200")
Daniel Martín <mardani29@yahoo.es> writes:
> In the same header that defines SIG2STR_MAX there is SIGNUM_BOUND. It
> is defined depending on the availability of other macros, including
> NSIG. Couldn't it be used instead?
If I understand correctly, SIG2STR_MAX is also defined by the OS
sig2str:
/* Don't override system declarations of SIG2STR_MAX, sig2str, str2sig. */
#ifndef SIG2STR_MAX
So we're free to use SIG2STR_MAX on all systems (because it's either
defined by gnulib or the OS). Is the same the case for SIGNUM_BOUND?
(It might just be defined by gnulib.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-27 10:55 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 [this message]
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
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=87ilomwf3a.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=luangruo@yahoo.com \
--cc=mardani29@yahoo.es \
/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.