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: Thu, 20 Aug 2015 14:31:49 +0200	[thread overview]
Message-ID: <871teyi1je.fsf@gnu.org> (raw)
In-Reply-To: <6sw6c7y4h6qhwl.fsf@pfdstudio.com> (Peter Davis's message of "Thu, 20 Aug 2015 08:11:06 -0400")

Peter Davis <pfd@pfdstudio.com> writes:

>> Strange.  I can use that here and it works, i.e., it marks the
>> current article as expirable and then selects the next one if there's
>> any.  No errors.
>
> So that suggests that the problem is not in the macro definition at
> all, but in some function that's getting invoked by it.

It means that `E' is not bound to a command when the macro is executed,
and I have no clue how that can happen because you said that `E' works
when you do it manually, i.e., press just `E' in the summary buffer.

> Maybe I need to completely remove and re-install gnus or Aquamacs or
> both.

I don't think this is or can be caused by a broken Gnus install but of
course try.  And let us know if you could fix the issue.

> I notice, though, from my limited understanding of lisp, it appears
> the recorded macro still depends on the definition of the "E" key,
> rather than invoking a lisp function directly. I can try re-recording
> it just using function calls.

Yes, it does.  A keyboard macro just does exactly what you have been
recording, so when you press `E', it'll record that.  When you do `M-x
gnus-summary-mark-as-expirable RET', it'll record that.  Both macros
have the same effect but the former will break if the binding changes
(unlikely), and the second one will break if the command name changes
(even more unlikely).

>> Sorry, now I'm running out of ideas...
>
> I was out of ideas when I started this thread, so thank you for
> keeping this alive, and for the wealth of information you've provided
> along the way.

You're welcome!

Bye,
Tassilo



  reply	other threads:[~2015-08-20 12:31 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
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 [this message]
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=871teyi1je.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).