From: Stefan Kangas <stefankangas@gmail.com>
To: Daniel Semyonov <daniel@dsemy.com>, Eli Zaretskii <eliz@gnu.org>
Cc: Christopher Howard <christopher@librehacker.com>, 74857@debbugs.gnu.org
Subject: bug#74857: 30.0.92; Gnus nnatom: url protocol
Date: Sun, 22 Dec 2024 01:29:42 +0000 [thread overview]
Message-ID: <CADwFkmkv4X646QSH5nzGYgASKsqMr2Adk35XkA67SeogDHjn1g@mail.gmail.com> (raw)
In-Reply-To: <87zfkpq9ay.fsf@dsemy.com>
Daniel Semyonov via "Bug reports for GNU Emacs, the Swiss army knife of
text editors" <bug-gnu-emacs@gnu.org> writes:
> This is a known issue (also noted in the manual), though the message
> returned should be more descriptive.
>
> The returned message is emitted by Gnus when it fails to get info for
> the server from the backend, and should use the value of
> 'backend-status-string' ('nnatom-status-string' in this case); this
> works on a normal session on my end (returning a message set in
> 'nnatom--read-feed'), but fails with emacs -Q, also returning "Couldn't
> request list: nil".
> I half suspect this is a bug with Gnus trying to read the status string
> of the wrong server (and not a bug in nnatom), but I'll look into it.
>
> As for why it isn't allowed in the first place, Gnus unfortunately
> breaks when ":" is used in server addresses due to regular expressions
> used in various internal functions, though I don't remember the details.
Does nnatom use http or https by default in these situations?
prev parent reply other threads:[~2024-12-22 1:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 19:13 bug#74857: 30.0.92; Gnus nnatom: url protocol Christopher Howard
2024-12-21 9:47 ` Eli Zaretskii
2024-12-21 16:40 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-22 1:29 ` Stefan Kangas [this message]
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=CADwFkmkv4X646QSH5nzGYgASKsqMr2Adk35XkA67SeogDHjn1g@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=74857@debbugs.gnu.org \
--cc=christopher@librehacker.com \
--cc=daniel@dsemy.com \
--cc=eliz@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.