From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: [gstupp@cisco.com: kmacro-bind-to-key does not bind to function keys]
Date: Sun, 08 Jul 2007 18:23:20 -0400 [thread overview]
Message-ID: <E1I7fA0-0001RX-6N@fencepost.gnu.org> (raw)
Would someone please DTRT, then ack?
------- Start of forwarded message -------
X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY
autolearn=failed version=3.1.0
Date: Sun, 8 Jul 2007 14:53:13 +0300
From: Gideon Stupp <gstupp@cisco.com>
To: bug-gnu-emacs@gnu.org
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=1547; t=1183895600;
x=1184759600; c=relaxed/simple; s=amsdkim1002;
h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version;
d=cisco.com; i=gstupp@cisco.com;
z=From:=20Gideon=20Stupp=20<gstupp@cisco.com>
|Subject:=20kmacro-bind-to-key=20does=20not=20bind=20to=20function=20keys
|Sender:=20; bh=lbJVRecmfXigonNTZ61o9tB7X/GOd7tacBxeU1hN3vI=;
b=FI4Sf1c70PJ8iIC/A3QAQFGvPKhWEsESibYveI5zOwlScOUOnOQGp0zHwvsME3Airv3DTu06
PCyuHhWf1lQ9hpDE72g976zjGyV3QyrLb2JRSwoRJjoYyhZ1oNZIZy2E;
Authentication-Results: ams-dkim-1; header.From=gstupp@cisco.com; dkim=pass (
sig from cisco.com/amsdkim1002 verified; );
Subject: kmacro-bind-to-key does not bind to function keys
kmacro-bind-to-key returns "call-interactively: Wrong type argument: number-or-marker-p, f12"
when trying to assign a macro to function key f12. Possible patch:
- --- /tmp/kmacro.el.orig 2007-07-08 14:48:17.000000000 +0300
+++ /tmp/kmacro.el 2007-07-08 14:49:01.000000000 +0300
@@ -793,7 +793,8 @@
(error "No keyboard macro defined"))
(let ((key-seq (read-key-sequence "Bind last macro to key: "))
ok cmd)
- - (when (= (length key-seq) 1)
+ (when (and (stringp key-seq)
+ (= (length key-seq) 1))
(let ((ch (aref key-seq 0)))
(if (or (and (>= ch ?0) (<= ch ?9))
(and (>= ch ?A) (<= ch ?Z)))
In GNU Emacs 22.1.1 (i686-pc-linux-gnu, X toolkit, Xaw3d scroll bars)
of 2007-07-08 on gstupp-lnx
Windowing system distributor `The X.Org Foundation', version 11.0.60802000
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US.UTF-8
locale-coding-system: utf-8
default-enable-multibyte-characters: t
Major mode: Help
Minor modes in effect:
shell-dirtrack-mode: t
which-function-mode: t
show-paren-mode: t
mouse-wheel-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
view-mode: t
_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------
reply other threads:[~2007-07-08 22:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1I7fA0-0001RX-6N@fencepost.gnu.org \
--to=rms@gnu.org \
--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).