all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: Chong Yidong <cyd@stupidchicken.com>, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: usr1-signal, usr2-signal, etc.
Date: Tue, 19 Dec 2006 10:48:17 +0100	[thread overview]
Message-ID: <m3zm9kb4im.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <wly7p4my35.wl%mituharu@math.s.chiba-u.ac.jp> (YAMAMOTO Mitsuharu's message of "Tue\, 19 Dec 2006 11\:14\:06 +0900")

YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp> writes:

>>>>>> On Mon, 18 Dec 2006 11:38:21 -0500, Chong Yidong <cyd@stupidchicken.com> said:
>
>> storm@cua.dk (Kim F. Storm) writes:
>>> So I would rather redefine them to single events (named sigusr1 and
>>> sigusr2 as those names are already known to the signal-process
>>> function), and handle them through special-event-map as you
>>> suggested.
>
>> In that case, is there a rationale for the rather large changes
>> checked into emacs.c, keyboard.c, and process.c over the last two
>> weeks?  Should they not be reverted?
>
> Do the "large changes" you think should be reverted include my
> 2006-12-14 changes?  These changes are not for the event format but
> for fixing a problem that has existed for a long time.  That is, about
> calling a non-reentrant function in a signal handler context while it
> is executed in a normal context.

Yes.  Those changes are very important on their own.

It still think that handling signals through special-event-map is
the proper (or the least problematic) thing to do.  So unless I
hear any objections, I'll make that change later this week.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2006-12-19  9:48 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-03  1:39 usr1-signal, usr2-signal, etc Kim F. Storm
2006-12-04  5:15 ` Richard Stallman
2006-12-04  9:05   ` Kim F. Storm
2006-12-04 13:08     ` Kim F. Storm
2006-12-05  1:45       ` Richard Stallman
2006-12-05  3:40       ` YAMAMOTO Mitsuharu
2006-12-05 22:26         ` David Kastrup
2006-12-05 22:51           ` Kim F. Storm
2006-12-08 10:28             ` YAMAMOTO Mitsuharu
2006-12-11  9:41               ` Kim F. Storm
2006-12-11 14:31                 ` YAMAMOTO Mitsuharu
2006-12-12  9:47                   ` Kim F. Storm
2006-12-12 13:32                     ` YAMAMOTO Mitsuharu
2006-12-12 13:54                       ` Kim F. Storm
2006-12-13  9:38                         ` YAMAMOTO Mitsuharu
2006-12-13 10:26                           ` Kim F. Storm
2006-12-14  9:14                             ` YAMAMOTO Mitsuharu
2006-12-14 11:23                               ` Kim F. Storm
2006-12-18 16:38                                 ` Chong Yidong
2006-12-19  2:14                                   ` YAMAMOTO Mitsuharu
2006-12-19  9:48                                     ` Kim F. Storm [this message]
2006-12-19 15:46                                       ` Kim F. Storm
2006-12-20 13:01                                       ` Richard Stallman
2006-12-20 15:58                                         ` Kim F. Storm
2006-12-12 21:46                       ` Richard Stallman
2006-12-06  0:46         ` Richard Stallman
2006-12-06  9:44       ` Johan Bockgård

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=m3zm9kb4im.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=rms@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 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.