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: Thu, 20 Aug 2015 08:57:34 -0400	[thread overview]
Message-ID: <6sw6c7r3myqfr5.fsf@pfdstudio.com> (raw)
In-Reply-To: <871teyi1je.fsf@gnu.org>

Tassilo Horn <tsdh@gnu.org> writes:

> 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.

I pressed 'E' when I was recording the macro, and it did expire the message.

>> 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'll try re-recording the macro using the gnus-summary-mark-as-expirable function and see if that helps.

>
> You're welcome!

And thank you again!

-pd



      reply	other threads:[~2015-08-20 12:57 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
2015-08-20 12:57                       ` Peter Davis [this message]

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=6sw6c7r3myqfr5.fsf@pfdstudio.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).