unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org,
	drew.adams@oracle.com, "Kim F. Storm" <storm@cua.dk>
Subject: Re: defcustom :type to use for a key sequence?
Date: Wed, 21 Dec 2005 09:31:52 +0100	[thread overview]
Message-ID: <85mziudf5z.fsf@lola.goethe.zz> (raw)
In-Reply-To: <E1EouBo-0003ry-QZ@fencepost.gnu.org> (Richard M. Stallman's message of "Tue, 20 Dec 2005 21:58:52 -0500")

"Richard M. Stallman" <rms@gnu.org> writes:

> With that change, your C-q replacement would have no disadvantages
> and might as well be installed.  But it does have a drawback as a
> solution to this problem: it isn't self-evident.  It would be
> something you just have to know.  That is not ideal.

How about S-C-q be an event-quote character in general?  Or at least
in contexts like Lisp buffers?  One can't type it on a tty, but since
you can't type interesting events on a tty anyway, this would not be a
drawback.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2005-12-21  8:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <DNEMKBNJBGPAOPIJOOICIEGFCOAA.drew.adams@oracle.com>
2005-12-14 16:44 ` defcustom :type to use for a key sequence? Drew Adams
2005-12-15  9:34   ` Kim F. Storm
2005-12-15 13:13     ` Lennart Borgman
2005-12-15 15:11       ` Kim F. Storm
2005-12-15 16:05         ` Lennart Borgman
2005-12-15 22:47           ` Kim F. Storm
2005-12-15 22:54             ` Lennart Borgman
2005-12-15 23:49             ` Kim F. Storm
2005-12-15 23:55               ` Lennart Borgman
2005-12-16 17:46               ` Richard M. Stallman
2005-12-20 14:53                 ` Kim F. Storm
2005-12-21  2:58                   ` Richard M. Stallman
2005-12-21  8:31                     ` David Kastrup [this message]
2005-12-16  0:51     ` Drew Adams
2005-12-20 15:06       ` Kim F. Storm
2005-12-20 17:32         ` Drew Adams

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=85mziudf5z.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=lennart.borgman.073@student.lu.se \
    --cc=storm@cua.dk \
    /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).