From: Greg Klanderman <gak@klanderman.net>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: emacs-devel@gnu.org
Subject: Re: gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods
Date: Tue, 26 Jan 2021 14:11:17 -0500 [thread overview]
Message-ID: <87r1m7ecoa.fsf@lwm.klanderman.net> (raw)
In-Reply-To: <87zh0w3llr.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 25 Jan 2021 10:41:36 -0800")
>>>>> On January 25, 2021 Eric Abrahamsen <eric@ericabrahamsen.net> wrote:
>> So maybe the real bug is just the documentation?
> I think so, I'm not aware of any code that is prepared to find a plain
> string inside `gnus-secondary-select-methods'. Maybe I'll open a bug for
> this just to make sure.
I can open one as well when I get back around to it.
>> And then I'll get back to Gnus..
> We'll be here :)
sounds good, thank you!
Greg
next prev parent reply other threads:[~2021-01-26 19:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-07 18:14 gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods Greg Klanderman
2021-01-08 18:28 ` Eric Abrahamsen
2021-01-18 18:07 ` Greg Klanderman
2021-01-21 23:50 ` Eric Abrahamsen
2021-01-25 17:51 ` Greg Klanderman
2021-01-25 18:41 ` Eric Abrahamsen
2021-01-26 19:11 ` Greg Klanderman [this message]
2021-01-26 10:51 ` Robert Pluim
2021-01-26 19:09 ` slow X11 frame creation and refresh after occlusion (was: gnus-server-to-method crash on virtual server name in gnus-secondary-select-methods) Greg Klanderman
2021-01-27 8:07 ` slow X11 frame creation and refresh after occlusion Robert Pluim
2021-01-30 19:32 ` Greg Klanderman
2021-02-01 8:56 ` Robert Pluim
2021-02-03 21:52 ` Greg Klanderman
2021-02-04 8:24 ` Robert Pluim
2021-02-04 21:14 ` Greg Klanderman
2021-02-05 9:53 ` Robert Pluim
2021-02-05 17:12 ` Greg Klanderman
2021-01-30 22:21 ` Greg Klanderman
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1m7ecoa.fsf@lwm.klanderman.net \
--to=gak@klanderman.net \
--cc=emacs-devel@gnu.org \
--cc=eric@ericabrahamsen.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).