Gnus development mailing list
 help / color / mirror / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: ding@gnus.org
Subject: Re: Macro suddenly broken
Date: Tue, 18 Aug 2015 08:28:06 -0400	[thread overview]
Message-ID: <6sw6c7a8towzl5.fsf@dhcp-6-148.hmco.com> (raw)
In-Reply-To: <87h9nx2g4z.fsf@gnu.org>

Tassilo Horn <tsdh@gnu.org> writes:

> 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.
>>
>> On the working system, 'M M e' is nothing, but 'M M e e' is:
>
> What does "nothing" mean?  I guess "the key sequence is not finished",
> right?

Nothing means that if I type 'M M e', emacs immediately responds that this is undefined, without waiting for any further keystrokes.

>
>>     ⇧M ⇧M E E runs the command gnus-summary-put-mark-as-expirable, which
>>    is an interactive Lisp function in `gnus-sum.el'.
>
> Anyway.  By default, `gnus-summary-put-mark-as-expirable' is not bound
> to a key, at least not in the current Gnus version.  Is it possible that
> you've bound it, e.g., in ~/.gnus.el, on the machine where the macro
> works?

It's not defined anywhere in my .emacs or .gnus.el file. In fact, the sequence originally came from an example Peter Münster posted
to this list, so it evidently worked for him.

> Well, what you can do of course is define your keyboard macro in such a
> way that it doesn't depend on key bindings, that is, the keyboard macro
> would do
>
>   M-x gnus-summary-put-mark-as-expirable RET...
>
> instead of
>
>   M M e e...

Yes, I'd have to figure out how to do the rest of the behavior (moving to and showing the next message in the group). As I
mentioned, I'm not lisp-savvy, but I could figure this out in time.

I'm still puzzled about why it suddenly stopped working, after being in use for months.

Thanks,
-pd



  reply	other threads:[~2015-08-18 12:28 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
2015-08-17 12:18       ` Peter Davis
2015-08-18  7:46         ` Tassilo Horn
2015-08-18 12:28           ` Peter Davis [this message]
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=6sw6c7a8towzl5.fsf@dhcp-6-148.hmco.com \
    --to=pfd@pfdstudio.com \
    --cc=ding@gnus.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.
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).