From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: 1580@debbugs.gnu.org, emacs-devel@gnu.org, jidanni@jidanni.org
Subject: Re: bug#1580: zap-to-char too raw, or document
Date: Wed, 20 Jul 2011 22:09:35 +0200 [thread overview]
Message-ID: <m3pql4ww74.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <87tyahvvts.fsf@stupidchicken.com> (Chong Yidong's message of "Wed, 20 Jul 2011 11:02:55 -0400")
Chong Yidong <cyd@stupidchicken.com> writes:
> Apart from zap-to-char, is there anything that might need this?
Perhaps not. We could just let that command read characters
specially...
> It's generally not worth it to add interactive codes for every
> conceivable operation. In this case, I think using read-char in the
> interactive form should work.
Will `read-char' allow zapping to `C-g'? It doesn't seem to be possible
to say `C-q C-g'...
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-20 20:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-14 15:28 bug#1580: zap-to-char too raw, or document jidanni
2011-07-10 14:26 ` Lars Magne Ingebrigtsen
2011-07-16 18:21 ` Lars Magne Ingebrigtsen
2011-07-16 18:21 ` Lars Magne Ingebrigtsen
2011-07-17 0:23 ` bug#1580: " Stephen J. Turnbull
2011-07-17 0:23 ` Stephen J. Turnbull
2011-07-17 8:01 ` David Kastrup
2011-07-17 9:34 ` Andreas Röhler
2011-07-17 11:18 ` Andreas Schwab
2011-07-17 17:36 ` Andreas Röhler
2011-07-18 13:39 ` Stephen J. Turnbull
2011-07-20 15:02 ` bug#1580: " Chong Yidong
2011-07-20 20:09 ` Lars Magne Ingebrigtsen [this message]
2011-07-21 16:19 ` Chong Yidong
2011-07-21 19:16 ` Glenn Morris
2011-07-21 19:16 ` Glenn Morris
2011-07-31 15:33 ` Lars Magne Ingebrigtsen
2011-07-31 15:33 ` Lars Magne Ingebrigtsen
2012-04-10 2:24 ` Lars Magne Ingebrigtsen
2012-04-10 2:24 ` Lars Magne Ingebrigtsen
2011-07-10 19:37 ` jidanni
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=m3pql4ww74.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=1580@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jidanni@jidanni.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.