From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: nnimap usage model
Date: Wed, 19 Feb 2003 12:04:53 +0100 [thread overview]
Message-ID: <84bs18wmy2.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <uwujxhdmo.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> kai.grossjohann@uni-duisburg.de (Kai Großjohann) writes:
>
>> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>>
>>> I'd say that the proper thing to do is to replace gnus-agent-cache
>>> with gnus-agent in gnus-agent-retrieve-headers (i.e. bind gnus-agent
>>> to nil) then delete gnus-agent-cache at all other references.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>> [...]
>>
>> It seems there is a misunderstanding. I'm looking at things from the
>> user's perspective. For this case, I think the questions we need to
>> answer are the following:
>>
>> (1) Under which circumstances does the agent write data to the local
>> disk? Which data does it write?
>>
>> (2) Under which circumstances does the agent read data from the local
>> disk? Which data does it read?
>>
>> Then we can formulate some documentation that helps the user.
>>
>> Another issue is whether the current Gnus behavior is correct or
>> should it be changed.
>
> I don't see these as being separate issues. If the current
> implementation is broken, and no one has noticed, then the feature
> must not be in wide spread use. If it isn't used, do we document how
> we think it should work (then fix the implementation) or do we remove
> the feature from the documentation? On the other hand, if the current
> implementation is working, how can we document it correctly if we
> can't agree on what it is doing?
Ah, I think I missed the crucial part: you were suggesting to
eliminate the variable gnus-agent-cache entirely. *blush*
So, is anyone using the combination of gnus-agent being t but
gnus-agent-cache being nil?
I think now I agree with your suggestion of just removing the
variable gnus-agent-cache.
I must spend more time to grok Kevin's postings.
I must spend more time to grok Kevin's postings.
I must spend more time to grok Kevin's postings.
I must spend more time to grok Kevin's postings.
--
A turnip curses Elvis
next prev parent reply other threads:[~2003-02-19 11:04 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 [this message]
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
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=84bs18wmy2.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).