Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: IMAP partial fetch
Date: Fri, 02 May 2003 22:46:43 -0400	[thread overview]
Message-ID: <3cjwsq5o.fsf@asfast.com> (raw)
In-Reply-To: <874r4ckhwg.fsf@egil.codesourcery.com> (Zack Weinberg's message of "Fri, 02 May 2003 17:12:15 -0700")

Zack Weinberg <zack@codesourcery.com> writes:

> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>
>> Hello
>>
>> Now that Oort is released, I'd like to throw some ideas in, which
>> features I as (primarily) a user would like to see in the next Gnus:
> ...
>
> [ ... partial imap fetch descriibed ... ]
>
> [ ... ]
> for messages where the user does want to look at the attachment, they
> are probably more willing to accept a lengthy download delay when they
> ask for the attachment to be saved, than when they ask to view the
> message.
>
> [ ... ]

I enthusiastically add my vote for this proposal, with the following
refinement: a group-specific variable could control whether these
attachments get downloaded as part of the entire message (as is done
now), or only when the user wants to see them.  This way, different
groups could be configured differently in this regard.  A configurable,
system-wide default setting could take effect if the group-specific
variable isn't set.

I think a cool related feature would be to download the IMAP4
BODYSTRUCTURE output of a message (in some suitably formatted manner)
along with the headers.  This way, the user could view the structure of
any message from the Summary buffer, and via a dialog, could optionally
request a subset of the parts to be actually downloaded.  A keystroke in
the Summary buffer could toggle the display of this structure for any
given message.

-- 
 Lloyd Zusman
 ljz@asfast.com



  parent reply	other threads:[~2003-05-03  2:46 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02 21:22 Ideas for .no Gnus Frank Schmitt
2003-05-02 23:48 ` Josh Huber
2003-05-08  9:23   ` Mike Woolley
2003-05-03  0:12 ` IMAP partial fetch (was Re: Ideas for .no Gnus) Zack Weinberg
2003-05-03  0:23   ` IMAP partial fetch Jody Klymak
2003-05-03  2:46   ` Lloyd Zusman [this message]
2003-05-03 16:59     ` Kai Großjohann
2003-05-07 20:42   ` Steinar Bang
2003-05-03  1:36 ` Ideas for .no Gnus Richard Hoskins
2003-05-03  5:02   ` Nevin Kapur
2003-05-12  0:03   ` Steve Youngs
2003-05-12  4:27     ` A.J. Rossini
2003-05-12  5:01     ` Richard Hoskins
2003-05-03  1:50 ` Ted Zlatanov
2003-05-03  2:29 ` A different spam model, which might be possible already (was Re: Ideas for .no Gnus) Zack Weinberg
2003-05-03 11:30   ` A different spam model, which might be possible already Ted Zlatanov
2003-05-04 16:39     ` Zack Weinberg
2003-05-04 22:32       ` Ted Zlatanov
2003-05-03 13:47   ` Andrew J. Korty
     [not found]   ` <m2llxo2lc3.fsf@ajk.local.>
2003-05-04 22:37     ` Ted Zlatanov
2003-05-03 17:13 ` Ideas for .no Gnus Kai Großjohann
2003-05-04 16:38   ` Lars Magne Ingebrigtsen
2003-05-05 13:17   ` Andreas Fuchs
2003-05-11 22:36   ` Alex Schroeder
2003-05-04  0:47 ` Nicer buttons (was: Ideas for .no Gnus) Jesper Harder
2003-05-04 13:59   ` Nicer buttons Julien Avarre
2003-05-04 14:15     ` luis fernandes
2003-05-04 14:52       ` Julien Avarre
2003-05-04 15:00       ` Jesper Harder
2003-05-05 17:23         ` luis fernandes
2003-05-04 16:41 ` Ideas for .no Gnus Lars Magne Ingebrigtsen
2003-05-05 13:12 ` Andreas Fuchs
2003-05-05 14:49   ` Kai Großjohann

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=3cjwsq5o.fsf@asfast.com \
    --to=ljz@asfast.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).