Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Peter Davis <pfd@pfdstudio.com>
Cc: ding@gnus.org
Subject: Re: Macro suddenly broken
Date: Fri, 14 Aug 2015 17:49:20 +0200	[thread overview]
Message-ID: <87tws1q39b.fsf@gnu.org> (raw)
In-Reply-To: <m2h9o2gc5q.fsf@PFDStudio-Air.home> (Peter Davis's message of "Fri, 14 Aug 2015 10:47:13 -0400")

Peter Davis <pfd@pfdstudio.com> writes:

> I've been using gnus for months on Aquamacs on a Mac OS X 10.10
> system, but suddenly, the 'd' macro that I've designed to mark a
> message as expirable and move to the next one is failing with:
>
>     After 0 kbd macro iterations: undefined: Keyboard macro terminated by a
> command ringing the bell
>
> I'm not aware of anything that's changed in my emacs or gnus setup. I
> have defined a macro that use 'd' for delete/next:
>
>     D runs the command [77 77 101 101 down 103], which is a keyboard macro.
>
>     It is bound to D.
>
>
>     Macro: 2*M 2*e <down> g
>
>     Keyboard macro.
>
> Any clues what might be going wrong here?

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.

Bye,
Tassilo



  parent reply	other threads:[~2015-08-14 15:49 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 [this message]
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
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=87tws1q39b.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).