From: Eli Zaretskii <eliz@gnu.org>
To: Dan Nicolaescu <dann@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: POSIX_SIGNALS support for GNU/Hurd?
Date: Thu, 01 Apr 2010 10:01:46 +0300 [thread overview]
Message-ID: <83mxxny7tx.fsf@gnu.org> (raw)
In-Reply-To: <yxqpr2knl24.fsf@fencepost.gnu.org>
> From: Dan Nicolaescu <dann@gnu.org>
> Date: Wed, 31 Mar 2010 19:11:31 -0400
>
> Besides src/s/gnu.h only w32 does not define POSIX_SIGNALS...
All these signals mean nothing to w32. AFAICS, we could simply define
empty no-ops for the functions Emacs uses under POSIX_SIGNALS, and
then w32 would not need any special conditions in these quarters.
Let me know if you want me to make this happen. (I guess it's only
worthwhile when the Hurd issue gets cleared.)
next prev parent reply other threads:[~2010-04-01 7:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-31 23:11 POSIX_SIGNALS support for GNU/Hurd? Dan Nicolaescu
2010-04-01 7:01 ` Eli Zaretskii [this message]
2010-04-30 20:54 ` Dan Nicolaescu
2010-05-01 18:42 ` Eli Zaretskii
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=83mxxny7tx.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=dann@gnu.org \
--cc=emacs-devel@gnu.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).