From: Tassilo Horn <tsdh@gnu.org>
To: Peter Davis <pfd@pfdstudio.com>
Cc: ding@gnus.org
Subject: Re: Macro suddenly broken
Date: Mon, 17 Aug 2015 09:19:15 +0200 [thread overview]
Message-ID: <87r3n2xtzg.fsf@gnu.org> (raw)
In-Reply-To: <6sw6c737zlyhdc.fsf@dhcp-6-148.hmco.com> (Peter Davis's message of "Fri, 14 Aug 2015 12:17:19 -0400")
Peter Davis <pfd@pfdstudio.com> writes:
>> Not really but what happens when you run the keyboard macro manually,
>> i.e., just press the sequence of keys defining it?
>>
>> The "ringing the bell" means that some error during movement
>> occurred, e.g., like pressing <down> when you are already on the last
>> line of the buffer.
>
> Thank you. On the non-working system, I type:
>
> M M e, but Emacs displays:
>
> ^M ^M E is undefined
Same here: M M e is undefined
I guess, that's already the reason. The keyboard macro fails because
the start of the macro's key sequence doesn't invoke any command.
> The definitions (and the .gnus.el files) are the same on the two systems:
>
> (defun pm/alter-summary-map ()
> (local-set-key "d" [?M ?M ?e ?e down ?g]))
>
> (defun pm/alter-article-map ()
> (local-set-key "d" "MMeen"))
Is is possible that you are running two different Gnus versions on the
two computers, i.e., in one version M M e is bound to something and in
one it is not? (I use the latest Gnus version from Git, and there M M
e is not bound neither in the summary nor in the article buffer.)
Anyway, what does `C-h k M M e' show in a summary/article buffer on the
computer where your macro still works?
Bye,
Tassilo
next prev parent reply other threads:[~2015-08-17 7:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-14 14:47 Peter Davis
2015-08-14 15:01 ` Peter Davis
2015-08-14 15:49 ` Tassilo Horn
2015-08-14 16:17 ` Peter Davis
2015-08-15 13:06 ` Peter Davis
2015-08-17 7:19 ` Tassilo Horn [this message]
2015-08-17 12:18 ` Peter Davis
2015-08-18 7:46 ` Tassilo Horn
2015-08-18 12:28 ` Peter Davis
2015-08-18 14:10 ` Tassilo Horn
2015-08-19 23:23 ` Peter Davis
2015-08-20 5:01 ` Tassilo Horn
2015-08-20 12:11 ` Peter Davis
2015-08-20 12:31 ` Tassilo Horn
2015-08-20 12:57 ` Peter Davis
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=87r3n2xtzg.fsf@gnu.org \
--to=tsdh@gnu.org \
--cc=ding@gnus.org \
--cc=pfd@pfdstudio.com \
/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.
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 NNTP newsgroup(s).