From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/88620 Path: news.gmane.org!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.gnus.general Subject: Re: Calling for testers: scratch/gnus-decoded branch Date: Sun, 16 Jun 2019 13:57:49 -0700 Message-ID: <87v9x5b642.fsf@ericabrahamsen.net> References: <875zpsycy4.fsf@ericabrahamsen.net> <87a7etnhla.fsf@tullinup.koldfront.dk> <87imtecbtw.fsf@ericabrahamsen.net> <87k1dlzmra.fsf@tullinup.koldfront.dk> <875zp5cvyx.fsf@ericabrahamsen.net> <87blyxz6x0.fsf@tullinup.koldfront.dk> <871rztco0s.fsf@ericabrahamsen.net> <87v9x5nvun.fsf@tullinup.koldfront.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: blaine.gmane.org; posting-host="blaine.gmane.org:195.159.176.226"; logging-data="34556"; mail-complaints-to="usenet@blaine.gmane.org" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux) To: ding@gnus.org Original-X-From: ding-owner+M36823@lists.math.uh.edu Sun Jun 16 22:58:39 2019 Return-path: Envelope-to: ding-account@gmane.org Original-Received: from lists1.math.uh.edu ([129.7.128.208]) by blaine.gmane.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hccEZ-0008qR-6u for ding-account@gmane.org; Sun, 16 Jun 2019 22:58:39 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.math.uh.edu) by lists1.math.uh.edu with smtp (Exim 4.92) (envelope-from ) id 1hccE3-0006df-TO; Sun, 16 Jun 2019 15:58:07 -0500 Original-Received: from mx2.math.uh.edu ([129.7.128.33]) by lists1.math.uh.edu with esmtps (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hccDx-0006ax-Uw for ding@lists.math.uh.edu; Sun, 16 Jun 2019 15:58:01 -0500 Original-Received: from quimby.gnus.org ([80.91.231.51]) by mx2.math.uh.edu with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from ) id 1hccDw-0006zM-AJ for ding@lists.math.uh.edu; Sun, 16 Jun 2019 15:58:01 -0500 Original-Received: from [195.159.176.226] (helo=blaine.gmane.org) by quimby.gnus.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from ) id 1hccDt-00069a-0H for ding@gnus.org; Sun, 16 Jun 2019 22:57:59 +0200 Original-Received: from list by blaine.gmane.org with local (Exim 4.89) (envelope-from ) id 1hccDr-0007zr-CR for ding@gnus.org; Sun, 16 Jun 2019 22:57:55 +0200 X-Injected-Via-Gmane: http://gmane.org/ Cancel-Lock: sha1:JZTrGbdlUPEbbHXTzoM4Pu30tE4= List-ID: Precedence: bulk Xref: news.gmane.org gmane.emacs.gnus.general:88620 Archived-At: Adam Sjøgren 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). > Come to think of it, Feedbase might be doing things wrong with regards > to encoding, as I didn't give it any thought. > > I hope I haven't sent you out on a wild goose chase here.) I wouldn't think so -- there are so few non-ascii nntp group names out there, I'm not sure what policy is. And if it worked before my changes, it should certainly work after! I'll keep trying to connect to feedbase. Thanks, Eric