From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 18198@debbugs.gnu.org
Subject: bug#18198: Gnus fails to read ~/.newsrc with group names which are not symbols
Date: Sat, 14 Feb 2015 19:27:43 +0800 [thread overview]
Message-ID: <87mw4gn368.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <878un3ckqx.fsf@violet.siamics.net>
Ivan Shmakov <ivan@siamics.net> writes:
>>>>>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>>>>> Ivan Shmakov <ivan@siamics.net> writes:
>
> […]
>
> >> I didn’t. 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.
>
> > This was discussed on the gnus.general list, and I produced a fix for
> > it (at least, I'm 95% sure it's the same issue),
>
> It isn’t, – the one #18198 is about is that Gnus fails to read
> ~/.newsrc it produces back; the one you suggest a patch for is
> about the (mis)use of ‘read’ in the Gnus IMAP implementation.
Ah, my apologies -- just a similar-looking problem, then.
> > and then apparently never sent the patch to the list, despite having
> > thought I did. Attaching the patch here.
>
> I believe that the information regarding (possible) bugs –
> including patches – should be sent to the BTS /first./
>
> This way, it’s easier to add late follow-ups, /and/ it still
> ends up in a mailing list (the bug-gnu-emacs@ one, that is.)
Sorry, didn't quite understand this -- did you mean just start another
bug report?
next prev parent reply other threads:[~2015-02-14 11:27 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 [this message]
2015-02-15 4:42 ` Lars Ingebrigtsen
2015-02-15 5:52 ` Ivan Shmakov
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=87mw4gn368.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.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.