Gnus development mailing list
 help / color / mirror / Atom feed
From: kgreiner@xpediantsolutions.com
Subject: Re: Equivalent of gnus-agent-fetch-groups from summary buffer
Date: Sat, 14 Dec 2002 00:03:55 -0600	[thread overview]
Message-ID: <un0n9m910.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <843cp2kjxh.fsf@lucy.cs.uni-dortmund.de>

kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:

> Is there something that does what `J u' in the group buffer does, only
> in the summary buffer?  (It might be best to bind that to `J u', as
> well.)  I find that I constantly exit a group then fetch then re-enter
> the group.
>
> Also, I think that `J g' might be a better mnemonic for fetching, by
> analogy with `g'.
>
> Opinions?
> -- 
> ~/.signature is: umop ap!sdn    (Frank Nobis)

Well, I did add 'J s' to the summary buffer.  My thoughts were that 'J
s' in the group buffer performs bulk fetching of articles matching a
preset condition.  In the summary buffer, the new 'J s' does bulk
fetching of manually selected articles.  I didn't use automatic
article selection based on the assumption that, if you liked to do
that sort of thing, you would do so before entering the group.  The
intent of this command was to support selective fetching.

One other major difference, gnus-agent-summary-fetch-series fetches
articles marked by the process mark.  That way, I was able to leverage
the existing commands for setting the process mark.

As for the binding, I'm game, but I suspect that most people like what
they are used to using.  If you do change the binding, don't forget to
consider changing 'J s' (gnus-agent-fetch-session) to conform to the
new scheme.

Kevin



  reply	other threads:[~2002-12-14  6:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13 15:39 Kai Großjohann
2002-12-14  6:03 ` kgreiner [this message]
2002-12-14 12:57   ` Kai Großjohann
2003-01-06  7:33 ` kgreiner

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=un0n9m910.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).