From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Emacs 28.2 gnus: nntp read marks lost after going offline and online again
Date: Thu, 22 Jun 2023 18:55:35 +0200 [thread overview]
Message-ID: <87r0q3qvw8.fsf@dod.no> (raw)
In-Reply-To: <87legcctx9.fsf@ericabrahamsen.net>
>>>>> Eric Abrahamsen <eric@ericabrahamsen.net>:
> I'm glad you worked it out, and sorry for maligning Gnus cloud!
No worries! :-)
I just wish it had more users, so I didn't feel so alone...:-)
I wonder where Ted Zlatanov (the original author of gnus-cloud and its
predecessor gnus-sync), is these days?
> I guess with a few decades of personal config, some of it is bound to go stale...
Yep! I dread every emacs major release. :-)
next prev parent reply other threads:[~2023-06-22 16:56 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-19 14:52 Steinar Bang
2023-06-19 16:27 ` Steinar Bang
2023-06-19 17:44 ` Steinar Bang
2023-06-19 18:16 ` dick
2023-06-20 17:00 ` Steinar Bang
2023-06-20 18:03 ` dick
2023-06-19 20:09 ` Steinar Bang
2023-06-20 19:24 ` Steinar Bang
2023-06-20 19:52 ` Steinar Bang
2023-06-21 1:39 ` Eric Abrahamsen
2023-06-21 18:46 ` Steinar Bang
2023-06-21 19:54 ` Steinar Bang
2023-06-21 20:05 ` Steinar Bang
2023-06-21 20:45 ` Steinar Bang
2023-06-21 20:55 ` Steinar Bang
2023-06-21 22:49 ` Eric Abrahamsen
2023-06-22 16:55 ` Steinar Bang [this message]
2023-06-25 14:21 ` Steinar Bang
2023-06-22 13:52 ` Dan Christensen
2023-06-24 5:52 ` Steinar Bang
2023-06-25 13:34 ` Dan Christensen
2023-06-25 14:35 ` Steinar Bang
2023-06-26 0:58 ` list level not respected by gnus-group-get-new-news [was: Emacs 28.2 gnus: nntp read marks lost after going offline and online again] Dan Christensen
2023-06-27 17:13 ` Steinar Bang
2023-06-19 16:37 ` Emacs 28.2 gnus: nntp read marks lost after going offline and online again dick
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=87r0q3qvw8.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@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).