Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Never mind
Date: 28 May 1997 08:37:25 +0200	[thread overview]
Message-ID: <m2hgfohzkq.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Stainless Steel Rat's message of 27 May 1997 18:57:40 -0400

Stainless Steel Rat <ratinox@peorth.gweep.net> writes:

> A new type of tick mark, "marked for download" should be created.  Setting
> this mark on an article will put it in line to be retrieved from the
> server;

Yes, this is implemented.

> setting this mark on a group (in the group buffer) will cause all
> articles in the group to be marked for download.

Uhm...  This would be for groups that aren't usually covered by the
agent, I guess?

The Gnus agent now works on a virtual server basis.  You go to the
server buffer and add the servers you want to the agent.  Then (the
next time you ask it to download) it'll do all the groups belonging to
those servers.

> The scoring routines or an extension thereof should be capable of
> setting this mark in some fashion.

I don't see why.  If you want downloading based on scoring, you just
use the agent scoring mechanism.

> It should *NOT* be tied to the 'D' key in any fashion. :) How about
> '@'?

I've added a tertiary mark that's bound to `J #'.  (All the agent
commands in all buffers are on the `J' submap.)

> Some means of readilly distinguishing downloaded messages from those for
> which only headers exist locally needs to be created, even on displays
> incapable of color or font changes.

Yes.  The way it does this now is by marking the undownloaded articles
as read.

> It should also be possible to "clump" downloaded articles at the top
> (or bottom, or maybe wherever) of the summary buffer, optionally
> overriding threading.

I think that wouldn't be very useful.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


  parent reply	other threads:[~1997-05-28  6:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-05-27 16:11 Lars Magne Ingebrigtsen
1997-05-27 16:24 ` Kai Grossjohann
1997-05-27 17:50   ` Lars Magne Ingebrigtsen
     [not found]     ` <x7iv04seu3.fsf@peorth.gweep.net>
1997-05-28  6:37       ` Lars Magne Ingebrigtsen [this message]
1997-05-28  7:55         ` Steinar Bang
1997-05-28  9:00           ` Lars Magne Ingebrigtsen
     [not found]             ` <x7vi43dzn2.fsf@peorth.gweep.net>
1997-05-29  7:48               ` Lars Magne Ingebrigtsen
     [not found]                 ` <x7u3jmmd1k.fsf@peorth.gweep.net>
1997-05-29 21:41                   ` Lars Magne Ingebrigtsen
1997-05-30  3:12                     ` Don Croyle
1997-05-30 20:32                       ` Lars Magne Ingebrigtsen
     [not found]                         ` <wkk9kgijet.fsf@peorth.gweep.net>
1997-05-31 11:41                           ` Lars Magne Ingebrigtsen
1997-05-28 15:43     ` Kai Grossjohann
1997-05-28 17:14       ` Hrvoje Niksic
     [not found]         ` <x74tbnbedo.fsf@peorth.gweep.net>
1997-05-29  7:45           ` Lars Magne Ingebrigtsen

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=m2hgfohzkq.fsf@proletcult.slip.ifi.uio.no \
    --to=larsi@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).