From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Trying to use gnus-cloud: what's the pinentry dialog? (and how can I get rid of it?)
Date: Fri, 24 Sep 2021 22:18:49 +0200 [thread overview]
Message-ID: <867df5wwuu.fsf@dod.no> (raw)
In-Reply-To: <87a6k2qsce.fsf@ucl.ac.uk>
>>>>> Eric S Fraga <e.fraga@ucl.ac.uk>:
> He probably should but *I* am kind of enjoying watching this play out!
Rest assured I have no plans of changing the habits of a lifetime,
whatever some n00b may think.
I am no closer to getting the blasted thing working, though.
I gave up getting cloud gnus to work when it was introduced in 2016, and
continued to use Ted Zlatanov's 2011 vintage gnus-sync.
However... one thing that made gnus-sync continue to work, was me having
a 2016 git gnus still in the load-path (gnus-sync needed stuff from the
old gnus).
However things seemed to sort of, kind of work, so I have procrastinated
on getting rid of gnus-sync.
However, with emacs 27, introduced on the debian bullseye upgrade,
things started to break.
So both gnus-sync and the old git gnus have been scrubbed from my emacs
config.
So I either learn to live without gnus syncing... or I get cloud gnus to
work.
The first is not an option, so here we are.
Can't be many users of cloud gnus, based on the responses on the
problems in 2016 and the second time I tried in 2020.
I think maybe Lars uses cloud gnus, and probably Ted, but neither of
them are much to see around here, these days.
Next step out is to read the source code and start debugging to see
what's actually going on (but that won't happen tonight).
next prev parent reply other threads:[~2021-09-24 20:19 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-19 13:50 Steinar Bang
2021-09-19 14:16 ` Steinar Bang
2021-09-19 14:30 ` Steinar Bang
2021-09-19 14:47 ` Steinar Bang
2021-09-23 15:07 ` Steinar Bang
2021-09-23 15:25 ` Steinar Bang
2021-09-23 17:17 ` Steinar Bang
2021-09-23 17:42 ` Steinar Bang
2021-09-23 17:58 ` dick
2021-09-24 8:40 ` Eric S Fraga
2021-09-24 20:18 ` Steinar Bang [this message]
2021-09-26 15:44 ` Eric S Fraga
2021-09-26 16:52 ` Steinar Bang
2021-09-27 14:54 ` Eric S Fraga
2021-10-02 11:27 ` Steinar Bang
2021-10-02 11:39 ` Steinar Bang
2021-10-02 14:59 ` Steinar Bang
2021-10-02 15:49 ` Eric Abrahamsen
2021-10-02 16:19 ` Steinar Bang
2021-10-03 8:46 ` Steinar Bang
2021-10-03 17:30 ` Steinar Bang
2021-10-04 14:43 ` Steinar Bang
2021-10-04 18:00 ` Steinar Bang
2021-10-04 19:19 ` Steinar Bang
2021-10-04 19:42 ` Steinar Bang
2021-10-04 20:09 ` Adam Sjøgren
2021-10-04 21:26 ` Steinar Bang
2021-10-05 8:41 ` Robert Pluim
2021-10-05 15:02 ` Adam Sjøgren
2021-10-05 15:41 ` Robert Pluim
2021-10-05 16:20 ` Adam Sjøgren
2021-10-05 15:14 ` Eric Abrahamsen
2021-10-05 16:17 ` Adam Sjøgren
2021-10-05 17:46 ` Eric Abrahamsen
2021-10-05 17:52 ` Adam Sjøgren
2021-09-23 17:14 ` Steinar Bang
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=867df5wwuu.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).