From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Does Gnus read and sync the read with IMAP?
Date: Fri, 20 Oct 2023 15:46:13 -0700 [thread overview]
Message-ID: <87lebw7w0a.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <48102.5036818878$1697837027@news.gmane.org>
Björn Bidar <bjorn.bidar@thaodan.de> writes:
> Dan Christensen <jdc@uwo.ca> writes:
>
>> On Oct 20, 2023, Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>>
>>> Dan Christensen <jdc@uwo.ca> writes:
>>>
>>>> Here's a followup question: how can I make Gnus update the marks
>>>> for
>>>> *all* IMAP groups.
>>>
>>> I once asked Lars about this -- since the IMAP server should be the
>>> source of truth for all information about the messages, why does
>>> Gnus
>>> store its own marks data for IMAP groups at all? Why not just
>
> How many imap server support imap metadata? Clients such as Thunderbird
> already safe their metadata in imap.
>
>>> refresh
>>> from the server at each startup? I think he said that for many large
>>> groups that would end up being prohibitively slow.
>>
>> I agree that it would be too slow for many people, especially with
>> remote IMAP servers. So I'd like an optional setting. But I don't
>> think it should have anything to do with Gnus shutdown and startup.
>
> Why would it be to slow? Other mail clients fetch the read
> status for each mail when they update the state of each
> imap mailbox.
I have never tried it, so I don't know if it would be slow or not. But
this wouldn't just update the read status, this would remove all
existing marks and refresh them from the server: ticks, replied,
forwarded, everything. I could imagine that being pretty slow.
next prev parent reply other threads:[~2023-10-20 22:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20416.4865355537$1697735647@news.gmane.org>
2023-10-20 13:28 ` Dan Christensen
2023-10-20 14:11 ` Eric Abrahamsen
2023-10-20 15:36 ` Dan Christensen
2023-10-20 21:23 ` Björn Bidar
[not found] ` <48102.5036818878$1697837027@news.gmane.org>
2023-10-20 22:46 ` Eric Abrahamsen [this message]
[not found] <65316d26.050a0220.cf46d.a86aSMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-19 20:10 ` Bob Newell
2023-10-19 22:06 ` Björn Bidar
[not found] ` <6531aa57.050a0220.a965a.55e5SMTPIN_ADDED_BROKEN@mx.google.com>
2023-10-19 22:45 ` Bob Newell
2023-10-20 0:57 ` Michael Heerdegen
2023-10-20 2:58 ` Bob Newell
2023-10-20 4:26 ` Michael Heerdegen
2023-10-20 14:04 ` Eric Abrahamsen
2023-10-20 19:09 ` Bob Newell
2023-10-20 19:28 ` Bob Newell
2023-10-20 21:18 ` Björn Bidar
2023-10-20 20:14 ` Adam Sjøgren
2023-10-22 22:29 ` James Thomas
2023-11-05 22:31 ` Adam Sjøgren
2023-10-20 13:12 ` Björn Bidar
2023-10-19 17:13 Björn Bidar
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=87lebw7w0a.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.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).