From: Paul Eggert <eggert@cs.ucla.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 12471@debbugs.gnu.org, lekktu@gmail.com
Subject: bug#12471: Avoid some signal-handling races, and simplify.
Date: Sat, 22 Sep 2012 02:40:41 -0700 [thread overview]
Message-ID: <505D8799.8030905@cs.ucla.edu> (raw)
In-Reply-To: <83haqqwhhv.fsf@gnu.org>
On 09/22/2012 02:10 AM, Eli Zaretskii wrote:
> Which means 'sys_kill' will need to do everything that's expected from
> 'raise'.
Unless I'm missing something, the only thing that Emacs will
expect from 'raise' is that it act like 'sys_kill' on itself,
so the proposed patch shouldn't affect what 'sys_kill' needs
to do.
> I was asking not to aggravate the situation, if it's possible.
Yes, but I don't see how the proposed patch aggravates the
situation. It causes Emacs to execute the same Windows
primitives as before. These primitives may have problems,
but those problems are the same problems as before.
I'm perhaps stating the obvious here, but just in case
I'm misunderstanding please bear with me: the Windows
substitutes for kill, raise, etc. need not support every
POSIX feature. They need to support only the features that
Emacs uses. So sys_raise need not support every feature that
POSIX requires for 'raise'; it needs to support only the
'raise' features that Emacs uses. Likewise for 'sys_kill'
versus POSIX 'kill'.
next prev parent reply other threads:[~2012-09-22 9:40 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-18 23:39 bug#12471: Avoid some signal-handling races, and simplify Paul Eggert
2012-09-19 16:18 ` Eli Zaretskii
2012-09-20 6:07 ` Paul Eggert
2012-09-20 17:44 ` Eli Zaretskii
2012-09-21 7:42 ` Paul Eggert
2012-09-21 8:31 ` Eli Zaretskii
2012-09-21 17:26 ` Paul Eggert
2012-09-21 17:38 ` Eli Zaretskii
2012-09-21 18:13 ` Paul Eggert
2012-09-21 18:27 ` Eli Zaretskii
2012-09-21 19:59 ` Paul Eggert
2012-09-22 8:02 ` Eli Zaretskii
2012-09-22 8:47 ` Paul Eggert
2012-09-22 9:10 ` Eli Zaretskii
2012-09-22 9:40 ` Paul Eggert [this message]
2012-09-22 10:07 ` Eli Zaretskii
2012-09-22 10:55 ` Paul Eggert
2012-09-22 11:16 ` Eli Zaretskii
2012-09-22 20:28 ` Stefan Monnier
2012-09-22 21:55 ` Paul Eggert
2012-09-23 3:55 ` Eli Zaretskii
2012-09-23 3:52 ` Eli Zaretskii
2012-09-19 16:45 ` Jan Djärv
2012-09-19 19:58 ` Paul Eggert
2012-09-20 6:27 ` Jan Djärv
2012-09-19 21:36 ` Andy Moreton
2012-09-23 9:36 ` bug#12471: installed into trunk Paul Eggert
2012-09-23 15:22 ` Andy Moreton
2012-09-23 16:23 ` Andy Moreton
2012-09-23 17:37 ` Juanma Barranquero
2012-09-23 17:37 ` 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=505D8799.8030905@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=12471@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=lekktu@gmail.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 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).