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: Stefan Kangas <stefankangas@gmail.com>
Cc: Christopher Howard <christopher@librehacker.com>,
	Eli Zaretskii <eliz@gnu.org>,
	74857@debbugs.gnu.org
Subject: bug#74857: 30.0.92; Gnus nnatom: url protocol
Date: Sun, 22 Dec 2024 23:12:31 +0200	[thread overview]
Message-ID: <877c7ra0cg.fsf@dsemy.com> (raw)
In-Reply-To: <CADwFkmkv4X646QSH5nzGYgASKsqMr2Adk35XkA67SeogDHjn1g@mail.gmail.com> (Stefan Kangas's message of "Sun, 22 Dec 2024 01:29:42 +0000")

>>>>> Stefan Kangas writes:

    > 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?

nnatom always uses https, feeds available only over http are not
supported at all currently (unless they are downloaded separately, and
added to nnatom as a file instead of a URL).
This is something I wanted to address at some point but honestly forgot
about it, though I'm not sure how important it is TBH; adding a server
variable controlling this would be fairly easy to do, I think.

In any case I still haven't had time to look into the issue with the
wrong returned message, I'll look into both issues in a few days
(hopefully).

Daniel





      reply	other threads:[~2024-12-22 21:12 UTC|newest]

Thread overview: 5+ 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
2024-12-22 21:12       ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors [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

  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=877c7ra0cg.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 \
    --cc=stefankangas@gmail.com \
    /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).