From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Calling for testers: scratch/gnus-decoded branch
Date: Sun, 16 Jun 2019 14:25:16 -0700 [thread overview]
Message-ID: <87r27tb4ub.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87v9x5b642.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Adam Sjøgren <asjo@koldfront.dk> writes:
>
>> Eric writes:
>>
>>> Okay, that's useful information. Do you have `gnus-save-newsrc-file' set
>>> to t, and is this group saved in that file? If so, is the group name
>>> encoded or decoded?
>>
>> ,----[ C-h v gnus-save-newsrc-file RET ]
>> | gnus-save-newsrc-file is a variable defined in ‘gnus-start.el’.
>> | Its value is t
>> |
>> | Documentation:
>> | Non-nil means that Gnus will save the ‘.newsrc’ file.
>> | Gnus always saves its own startup file, which is called
>> | ".newsrc.eld". The file called ".newsrc" is in a format that can
>> | be readily understood by other newsreaders. If you don’t plan on
>> | using other newsreaders, set this variable to nil to save some time on
>> | exit.
>> |
>> | You can customize this variable.
>> `----
>>
>> I didn't know I had that set to t, but I have.
>>
>> The file is empty, though?!
>
> It's only used if your gnus-select-method is an nntp server, and then
> only for that server. I thought I remembered that your nntp server was a
> secondary one, but I wanted to make sure.
>
>> $ ls -l .newsrc
>> -rw-r--r-- 1 asjo asjo 0 May 30 2015 .newsrc
>>
>>> (I'm trying to test with feedbase.org but Gnus never succeeds in
>>> connecting to it).
>>
>> (Are you using nntps? There's no nntp-support on feedbase.org, only
>> nntps. I'm using this in my gnus-secondary-select-methods:
>>
>> (nntp "fb"
>> (nntp-open-connection-function nntp-open-tls-stream) ; feedbase does not do STARTTLS (yet?)
>> (nntp-port-number 563) ; nntps
>> (nntp-address "feedbase.org"))
>
> That's what I was trying to use! Hmm, maybe I was just being too
> impatient (and my internet connection sucks here).
Yup, it was both of those. I've managed to connect and test (and confirm
the bug), and just pushed a fix.
next prev parent reply other threads:[~2019-06-16 21:25 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 0:59 Eric Abrahamsen
2019-06-04 5:24 ` Eric Abrahamsen
2019-06-06 2:38 ` Michael Heerdegen
2019-06-06 2:48 ` Emanuel Berg
2019-06-06 23:07 ` Eric Abrahamsen
2019-06-07 3:24 ` Emanuel Berg
2019-06-07 3:58 ` Eric Abrahamsen
2019-06-07 4:15 ` Emanuel Berg
2019-06-07 5:44 ` Eric Abrahamsen
2019-06-07 15:22 ` Emanuel Berg
2019-06-07 16:52 ` Eric Abrahamsen
2019-06-08 21:01 ` Emanuel Berg
2019-06-06 9:14 ` Andy Moreton
2019-06-06 23:47 ` Eric Abrahamsen
2019-06-07 9:48 ` Tassilo Horn
2019-06-07 16:46 ` Eric Abrahamsen
2019-06-07 22:41 ` Adam Sjøgren
2019-06-10 4:18 ` Eric Abrahamsen
2019-06-16 13:24 ` Adam Sjøgren
2019-06-16 16:53 ` Eric Abrahamsen
2019-06-16 19:06 ` Adam Sjøgren
2019-06-16 19:45 ` Eric Abrahamsen
2019-06-16 20:01 ` Adam Sjøgren
2019-06-16 20:57 ` Eric Abrahamsen
2019-06-16 21:25 ` Eric Abrahamsen [this message]
2019-07-20 9:22 ` Adam Sjøgren
2019-07-21 3:19 ` Eric Abrahamsen
2019-07-21 10:08 ` Adam Sjøgren
2019-07-22 17:05 ` Eric Abrahamsen
2019-07-22 17:08 ` Adam Sjøgren
2019-06-16 19:45 ` Eric Abrahamsen
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=87r27tb4ub.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).