Gnus development mailing list
 help / color / mirror / Atom feed
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: Sun, 19 Sep 2021 16:30:04 +0200	[thread overview]
Message-ID: <86bl4ok58z.fsf@dod.no> (raw)
In-Reply-To: <86fsu0k5w3.fsf@dod.no>

>>>>> Steinar Bang <sb@dod.no>:

> I have now started a fresh emacs and in this emacs saving sync data does
> not require a pinentry.

> And the reason pinentry is gone, is that this customized setting was
> loaded: 
>  '(gnus-cloud-storage-method (quote base64-gzip))

> The setting is dated Sun Jul 24 16:57:04 2016 +0200 and was made because
> the default method EPG didn't work in Emacs 24.4 on windows (according to git
> blame).

> With emacs 26.3 EPG apparently works on widows, but has a very annoying
> pinentry dialog.

> I'll continue with base64-gzip.

And trying to "~-RET" on emacs 27.1 on debian bullseye gave me the error
message
 gnus-cloud-decode-data: Invalid base64 data

Which, if memory doesn't fail me, is the error message that stopped me
from starting to use gnus-cloud in August of 2016...?

What gnus-cloud-storage-method do others use?



  reply	other threads:[~2021-09-19 14:30 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 [this message]
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
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=86bl4ok58z.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).