From: James Thomas <jimjoe@gmx.net>
To: "Harry Putnam" <hput3@fastmail.fm>
Cc: ding@gnus.org
Subject: Re: using (`gnus-summary-universal-argument')
Date: Thu, 06 Apr 2023 05:31:15 +0530 [thread overview]
Message-ID: <87a5zlswtw.fsf@gmx.net> (raw)
In-Reply-To: <11306fbc-e44c-4f93-bf92-7fb4fc1b0d79@app.fastmail.com> (Harry Putnam's message of "Tue, 04 Apr 2023 09:41:50 -0400")
Harry Putnam wrote:
>> So you should simply try 'C-u 5037 J #' without anything before it.
>
> Did you actually try that? Because if you had you would know that it does not work.
> It seems mass marking Messages with the download mark is one of those rare
> things that require M-&
Works for me (with a small number). Btw those messages should already be
visible in the Summary buffer - else, try 'C-u 5037 / o' first.
--
prev parent reply other threads:[~2023-04-06 0:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 18:35 hput
2023-04-04 12:50 ` James Thomas
2023-04-04 13:41 ` Harry Putnam
2023-04-06 0:01 ` James Thomas [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=87a5zlswtw.fsf@gmx.net \
--to=jimjoe@gmx.net \
--cc=ding@gnus.org \
--cc=hput3@fastmail.fm \
/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).