unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: usr1-signal, usr2-signal, etc.
Date: Mon, 04 Dec 2006 10:05:26 +0100	[thread overview]
Message-ID: <m364csvxnt.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <E1Gr6B4-0005bb-Ts@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 04 Dec 2006 00\:15\:42 -0500")

Richard Stallman <rms@gnu.org> writes:

>     IMHO, the new signal events in emacs 22 are not done the right way.
>
>     To me, it would be cleaner to define them as [signal usr1], 
>     [signal usr2], etc.
>
> Do you mean that it would generate a sequence of two events,
> `signal' and `usr1', so that `signal' would act as a prefix char?

Exactly.

> I agree.  Please change it.

I'll do that.

>     Ok, there is currently no "etc" in emacs 22, but if we later
>     want to be able to catch more signals, this would be a cleaner
>     way to extend the interface.
>
> I don't understand what that refers to.

I was referring to the "etc." in the list in the previous paragraph.
Currently we only have usr1 and usr2 signals, but if we add more (the
"etc") later, this would be a cleaner interface for such extensions.

>
>     We could even allow numeric bindings, like [signal 10] for SIGUSR1,
>     and also variants like [signal SIGUSR1].
>
> I don't see how that would work.  The signal has to generate a certain
> sequence of events.  If it generates `signal' and `usr1',
> the second event is not `SIGUSR1' and it is not 10 (C-h).

You are right ... it looked like a good idea when I wrote it, but I
must have been sleepy.  :-)

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

  reply	other threads:[~2006-12-04  9:05 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 [this message]
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
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

  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=m364csvxnt.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --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).