Gnus development mailing list
 help / color / mirror / Atom feed
From: James Thomas <jimjoe@gmx.net>
To: hput <hput3@fastmail.fm>
Cc: ding@gnus.org
Subject: Re: using (`gnus-summary-universal-argument')
Date: Tue, 04 Apr 2023 18:20:54 +0530	[thread overview]
Message-ID: <87r0szerpt.fsf@gmx.net> (raw)
In-Reply-To: <874jpyjfn6.fsf@local.lan> (hput's message of "Sun, 02 Apr 2023 14:35:57 -0400")

hput wrote:

> It seems I'm unable to get the functionality the manual describes for
> (`gnus-summary-universal-argument')
>
> I position cursor at the top of a group of 5037 messages
>
> then press `Alt-Shift-&' (`gnus-summary-universal-argument') which displays `M-&'.
>
>
> then  press 'C-u 5037 J #'
>
>
> Which the manual says will mark the next 5037 message with `%' the
> gnus-agent-download mark

Here's what the manual says:

‘M-&’
     Perform any operation on all articles that have been marked with
     the process mark (‘gnus-summary-universal-argument’).

So it has to do with *process marked* articles. Btw, here's the
docstring of 'J #':

  Mark the next N articles as downloadable.
  If N is negative, mark backward instead. If UNMARK is non-nil, remove
  the mark instead. The difference between N and the actual number of
  articles marked is returned.

So you should simply try 'C-u 5037 J #' without anything before it.

> Further, once I have manually marked a number of messages with
> the `%' how to tell agent to go ahead and download them?
>
> Doing C-h b on summary buffer and searching in many ways .... first
> off finding all `gnus-agent ...' hits.   Checked for the word download, etc etc.
> but not finding anthing promissing.

The manual (C-h i C-s gnus) is a much better option. It says do 'J u'.

--
James


  reply	other threads:[~2023-04-04 15:27 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 [this message]
2023-04-04 13:41   ` Harry Putnam
2023-04-06  0:01     ` James Thomas

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=87r0szerpt.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).