From: Po Lu <luangruo@yahoo.com>
To: emacs-devel@gnu.org
Cc: Lars Ingebrigtsen <larsi@gnus.org>
Subject: Re: master ed84f24a21: Make `signal-process' allow completing over signal names
Date: Mon, 27 Jun 2022 09:20:26 +0800 [thread overview]
Message-ID: <87ilomewbp.fsf@yahoo.com> (raw)
In-Reply-To: <20220626204757.57AB1C01685@vcs2.savannah.gnu.org> (Lars Ingebrigtsen's message of "Sun, 26 Jun 2022 16:47:57 -0400 (EDT)")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> +DEFUN ("signal-names", Fsignal_names, Ssignal_names, 0, 0, 0,
> + doc: /* Return a list of known signal names on this system. */)
> + (void)
> +{
> + char name[SIG2STR_MAX];
> + Lisp_Object names = Qnil;
> + for (int i = 0; i < 255; ++i)
> + {
> + if (!sig2str (i, name))
> + {
> + names = Fcons (build_string (name), names);
> + }
> + }
> + return names;
> +}
> +
Shouldn't the "255" be NSIG instead? And what about systems where POSIX
signal handling doesn't really apply, such as MS Windows and MS-DOS?
Thanks.
next parent reply other threads:[~2022-06-27 1:20 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 ` Po Lu [this message]
2022-06-27 6:37 ` master ed84f24a21: Make `signal-process' allow completing over signal names 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
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=87ilomewbp.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--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 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.