From: Ivan Shmakov <ivan@siamics.net>
To: 18198@debbugs.gnu.org
Subject: bug#18198: Gnus fails to read ~/.newsrc with group names which are not symbols
Date: Sun, 15 Feb 2015 05:52:37 +0000 [thread overview]
Message-ID: <87d25bafh6.fsf@violet.siamics.net> (raw)
In-Reply-To: <87sie7bxav.fsf@building.gnus.org> (Lars Ingebrigtsen's message of "Sun, 15 Feb 2015 15:42:16 +1100")
>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>>>>> Lars Ingebrigtsen <larsi@gnus.org> writes:
>>> Well, "[Hello]/World" isn't a valid newsgroup name,
>> Yet (Hello)/World is. (Per the newsgroup-name and wildmat-exact
>> productions given in section 9.8 of RFC 3977.)
[…]
>> The person who brought this issue to IRC has apparently used
>> something like (nnimap "imap.gmail.com") for gnus-select-method.
>> Though indeed, I know of no reason /not/ to set
>> gnus-save-newsrc-file to nil in this case.
> There should only be newsgroups in the .newsrc file -- it's for
> interoperability with other newsreaders, and putting non-newsgroups
> in there makes no sense.
There still may be RFC-compliant newsgroup names which contain
parentheses; and alt.foo.(bar) would fail just the same as
[Hello]/World.
Granted, I know of no such /public/ newsgroups, but whoever
hosts an NNTP server could probably add a local one with ease.
> So that does sound like a bug.
As long as there’s no clear indication from Gnus that ~/.newsrc
could easily break when used together with nnimap (and possibly
other similar select methods), I’d rather deem it a bug in Gnus.
--
FSF associate member #7257 np. Bounzie boom — S. A. Kiviniemi B6A0 230E 334A
next prev parent reply other threads:[~2015-02-15 5:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 10:07 bug#18198: Gnus fails to read ~/.newsrc with group names which are not symbols Ivan Shmakov
2015-02-13 8:43 ` Lars Ingebrigtsen
2015-02-14 8:05 ` Ivan Shmakov
2015-02-14 10:41 ` Eric Abrahamsen
2015-02-14 10:55 ` Ivan Shmakov
2015-02-14 11:27 ` Eric Abrahamsen
2015-02-15 4:42 ` Lars Ingebrigtsen
2015-02-15 5:52 ` Ivan Shmakov [this message]
2017-01-25 18:24 ` Lars Ingebrigtsen
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=87d25bafh6.fsf@violet.siamics.net \
--to=ivan@siamics.net \
--cc=18198@debbugs.gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.