unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Semyonov via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 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: Sat, 21 Dec 2024 18:40:05 +0200	[thread overview]
Message-ID: <87zfkpq9ay.fsf@dsemy.com> (raw)
In-Reply-To: <865xnd8j12.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 21 Dec 2024 11:47:21 +0200")

>>>>> Eli Zaretskii writes:

    >> From: Christopher Howard <christopher@librehacker.com>
    >> Date: Fri, 13 Dec 2024 10:13:02 -0900
    >> 
    >> 
    >> 
    >> Hi. When setting up a new feed group with nnatom in Gnus, there is a
    >> little oddity: If I pass in the URL to the feed without the protocol
    >> specifier, i.e., without the "https://" it works fine. But if I try
    >> to include the protocol specifier, then I get a message: "Couldn’t
    >> request list: nil", and the group is not added. It doesn't trigger
    >> the debugger, even though "debug-on-error" is set t.
    >> 
    >> So, I frequently have to delete the "https://" part when I am copying and pasting from some link for an atom feed. This is a bother.
    >> 
    >> I don't know if this can be reproduced without Gnus already being setup, but an example process is:
    >> 
    >> (1) bring up Gnus group buffer
    >> (2) run gnus-group-browse-foreign-server (B)
    >> (3) nnatom <RET>
    >> (4) https://sachachua.com/blog/category/emacs/feed/atom/ <RET>

    > Daniel, any comments or suggestions?

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.

Daniel





  reply	other threads:[~2024-12-21 16:40 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 [this message]
2024-12-22  1:29     ` Stefan Kangas

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=87zfkpq9ay.fsf@dsemy.com \
    --to=bug-gnu-emacs@gnu.org \
    --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 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).