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: Thu, 23 Sep 2021 19:42:23 +0200 [thread overview]
Message-ID: <86czozw5mo.fsf@dod.no> (raw)
In-Reply-To: <86lf3nw6su.fsf@dod.no>
>>>>> Steinar Bang <sb@dod.no>:
> I will try gnus-cloud-storage-method "No encoding again", this time with
> only one emacs running on the machine synched to.
"~ RET" does something but not the right thing.
For one thing, it keeps adding stuff to the ~/.gnus.el that won't parse
when starting up gnus:
diff --git a/.gnus.el b/.gnus.el
index 37f83f9dda..27dcd733bf 100644
--- a/.gnus.el
+++ b/.gnus.el
@@ -485,3 +485,16 @@ of the default NNTP server"
(defun sb-visit-privat ()
(interactive)
(sb-visit-all-groups-of-a-server "nnimap\\+privat:"))
+
+(:type :file :file-name "~/News/all.SCORE" :timestamp "2020-04-04T09:00:10+0200" :length 59)
+(("from"
+ ("Steinar Bang" nil nil s))
+ (decay 737519))
+
+(:type :file :file-name "~/News/nndoc_SCORE" :timestamp "2015-02-10T01:14:36+0100" :length 18)
+((decay 735639))
+
+(:type :file :file-name "~/News/nndoc_nnimap+privat_dod-27817.SCORE" :timestamp "2019-06-04T16:41:46+0200" :length 18)
+((decay 737214))
+
+(:type :file :file-name "~/News/nndraft_SCORE" :timestamp "2014-12-31T12:00:28+0100" :
\ No newline at end of file
What is this stuff and why is it re-added to ~/.gnus.el when I try to sync?
The nndoc and nndraft backends I have not added any sync for.
next prev parent reply other threads:[~2021-09-23 17:42 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 [this message]
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=86czozw5mo.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).