Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: nnimap usage model
Date: Thu, 20 Feb 2003 18:33:59 +0100	[thread overview]
Message-ID: <84vfzeg8l4.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <uk7fuapqy.fsf@boost-consulting.com>

David Abrahams <dave@boost-consulting.com> writes:

> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Well, err.  As I understand it, frobbing gnus-agent-cache influences
>
> Sorry: frobbing?

It's hacker jargon.  It means something like toggle: to frob a light
switch.  For details, see the jargon file (can be found via Google).

>> the behavior for the plugged case only.  So you could set
>> gnus-agent-cache to nil, then you could use `J s' to fetch articles
>> and headers.  But as long as you're online, Gnus won't use those
>> local copies when you enter a group and so on.  Instead, the headers
>> will be fetched again.  
>
> Seems rather pointless, doesn't it?

You'd be surprised.  Some people have uses for things that mere
mortals (like me) can't imagine.  Maybe somebody is running Emacs with
an NFS mounted home dir on a slow link where the server is on a faster
link.  Whatever...

But it's also the case that I fundamentally don't understand what Gnus
is doing -- see the discussion between Kevin and me regarding this.
-- 
A preposition is not a good thing to end a sentence with.



      reply	other threads:[~2003-02-20 17:33 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-10 22:16 David Abrahams
2003-02-11  7:08 ` Kai Großjohann
2003-02-11 16:51   ` David Abrahams
2003-02-11 18:39     ` Kai Großjohann
2003-02-11 20:05       ` David Abrahams
2003-02-11  8:25 ` Niklas Morberg
2003-02-11 16:36   ` Kai Großjohann
2003-02-11 16:55   ` David Abrahams
2003-02-11 18:17     ` Kevin Greiner
2003-02-11 20:03       ` David Abrahams
2003-02-12  2:45         ` David Abrahams
2003-02-12  5:16           ` Kevin Greiner
2003-02-15 11:10             ` David Abrahams
2003-02-15 15:56               ` Kevin Greiner
2003-02-16 14:32                 ` David Abrahams
2003-02-16 18:41                   ` Kevin Greiner
2003-02-16 20:51                     ` Kai Großjohann
2003-02-16 23:15                       ` Kevin Greiner
2003-02-17 16:23                         ` Kai Großjohann
2003-02-18 14:22                           ` Kevin Greiner
2003-02-19 11:04                             ` Kai Großjohann
2003-02-19 12:11                               ` Simon Josefsson
2003-02-21  8:00                                 ` Kevin Greiner
2003-02-25  4:08                                   ` gnus-agent-cache is broken Kevin Greiner
2003-03-05  3:52                                     ` FIXED: gnus-agent-cache Kevin Greiner
2003-02-17  8:34                       ` nnimap usage model Andreas Fuchs
2003-02-17 16:40                         ` Kai Großjohann
2003-02-17 19:06                           ` Andreas Fuchs
2003-02-15 17:58               ` Kai Großjohann
2003-02-16 14:35                 ` David Abrahams
2003-02-16 15:41                   ` Kai Großjohann
2003-02-20 16:19                     ` David Abrahams
2003-02-20 17:33                       ` Kai Großjohann [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=84vfzeg8l4.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@uni-duisburg.de \
    /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).