From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: none
Date: Sun, 05 Jun 2005 18:49:17 +0200 [thread overview]
Message-ID: <m33brw7nqq.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200506040056.j540uRr07626@raven.dms.auburn.edu> (Luc Teirlinck's message of "Fri, 3 Jun 2005 19:56:27 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> Is there a reason why this-original-command, unlike this-command,
> returns a non-nil value when no command is running?
It is an oversight. Please install your patch. Thanks.
> The reason why
> this originally annoyed me is no longer valid, so I do not need this
> to be "fixed", but I thought that maybe it might just be due to an
> oversight. What about the patch below? Grepping shows that
> this-original-command, is only used in ido and cua. Basically, I
> believe that only Kim has ever used it.
Maybe because until now, I'm the only one(?) who has seriously used
the new command remapping feature :-)
> What about the mini-patch
> below? I can install if desired.
>
> ===File ~/keyboard.c-diff===================================
> *** keyboard.c 26 May 2005 10:40:35 -0500 1.826
> --- keyboard.c 30 May 2005 17:14:15 -0500
> ***************
> *** 1522,1527 ****
> --- 1522,1528 ----
>
> Vthis_command = Qnil;
> real_this_command = Qnil;
> + Vthis_original_command=Qnil;
>
> /* Read next key sequence; i gets its length. */
> i = read_key_sequence (keybuf, sizeof keybuf / sizeof keybuf[0],
> ============================================================
>
>
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-06-05 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-04 0:56 (no subject) Luc Teirlinck
2005-06-05 16:49 ` Kim F. Storm [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-13 12:48 (unknown) Eli Zaretskii
2024-03-13 13:57 ` none Po Lu
2024-03-13 14:40 ` none Eric Abrahamsen
2022-07-21 11:36 (unknown) Gregory Heytings
2022-07-21 16:11 ` none Manuel Giraud
2021-12-20 2:29 (unknown) Davin Pearson
2021-12-20 14:13 ` none Stefan Monnier
2021-07-27 23:54 (unknown) Troy Hinckley
2021-07-30 21:33 ` none Stefan Monnier
2021-07-31 5:09 ` none Troy Hinckley
2021-07-31 16:22 ` none Stefan Monnier
2016-09-28 12:26 (unknown) Takesi Ayanokoji
2016-09-28 17:05 ` none John Wiegley
2003-03-07 12:04 None abrahamade
2002-11-28 17:01 iso-8859-1 and non-latin-1 chars Dave Love
2002-12-06 16:38 ` Dave Love
2002-12-10 23:47 ` Dave Love
2002-12-13 2:58 ` Kenichi Handa
2002-12-14 18:31 ` Richard Stallman
2002-12-17 11:41 ` None Kenichi Handa
2002-09-09 15:53 Text mode menu wishlist Sacha Chua
2002-09-09 17:27 ` Alex Schroeder
2002-09-10 1:45 ` Sacha Chua
2002-09-10 7:41 ` Thien-Thi Nguyen
2002-09-10 7:48 ` Miles Bader
2002-09-10 8:35 ` (no subject) Thien-Thi Nguyen
2002-09-10 8:47 ` none Miles Bader
2002-09-10 13:56 ` none Sacha Chua
2002-09-10 23:25 ` none Miles Bader
2002-09-30 5:59 ` none Sacha Chua
2002-10-01 6:18 ` none Richard Stallman
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=m33brw7nqq.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).