all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Daniel Semyonov <daniel@dsemy.com>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: emacs-devel@gnu.org
Subject: Re: Atom backend for Gnus (nnatom)
Date: Thu, 01 Jun 2023 00:02:34 +0300	[thread overview]
Message-ID: <87o7m0p639.fsf@dsemy.com> (raw)
In-Reply-To: <m34jns2sy6.fsf@fitzsim.org> (Thomas Fitzsimmons's message of "Wed, 31 May 2023 15:37:21 -0400")

>>>>> Thomas Fitzsimmons writes:

    > For comparison, the convenience function,
    > gnus-group-make-rss-group, asks for the blog title, with a
    > reasonable default suggestion, and the resulting line in *Group*
    > for my blog is:

    > nnrss:fitzsim's development log

    > With the procedure you suggested, I end up with:

    > nnatom+www.fitzsim.org/blog/?feed=atom:fitzsim's development log

    > FWIW, I prefer the former.  I think the +.. part is necessary for
    > stuff like email where the field after the ":" is frequently the
    > same (e.g., nnimap+mail.host1:INBOX, nnimap+mail.host2:INBOX)
    > whereas blog titles are usually unique, so the host/url designator
    > becomes redundant.

The procedure I suggested is pretty much the standard way to subscribe
to groups through Gnus.
Also, the '+...' part is necessary, nnrss doesn't need it for the same
reason it requires a special function to add groups.  If it really
bothers you customize the group line format.

    > Have you considered defining a `gnus-group-make-atom-group'
    > convenience function in nnatom.el (even though that's sort of a
    > namespace violation), and install a hook that binds that function
    > to a key in the *Group* buffer ("G A" seems to be available).

As I said before I have considered it, but not before fixing remaining
issues.  Honestly even then I don't really see why its so much more
convenient, other than it being familiar.
If you compare the two methods directly (G R <url> RET RET vs
B <url> RET u) they're very similar really.



  reply	other threads:[~2023-05-31 21:02 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-31  7:48 Atom backend for Gnus (nnatom) Daniel Semyonov
2023-05-31 14:08 ` Thomas Fitzsimmons
2023-05-31 15:45   ` Daniel Semyonov
2023-05-31 16:21     ` Thomas Fitzsimmons
2023-05-31 16:51       ` Daniel Semyonov
2023-05-31 18:33         ` Thomas Fitzsimmons
2023-05-31 18:50           ` Daniel Semyonov
2023-05-31 19:37             ` Thomas Fitzsimmons
2023-05-31 21:02               ` Daniel Semyonov [this message]
2023-05-31 21:11                 ` Thomas Fitzsimmons
2023-06-13  7:07 ` Daniel Semyonov
2023-06-13 11:22   ` Eli Zaretskii
2023-06-13 11:43     ` Arsen Arsenović
2023-06-13 13:34     ` Daniel Semyonov
2023-06-13 14:20   ` Thomas Fitzsimmons
2023-06-13 17:07     ` Eric Abrahamsen
2023-06-15  8:44       ` Eli Zaretskii
2023-06-18 15:53         ` Eric Abrahamsen
2023-06-19 11:11           ` Daniel Semyonov
2023-06-19 16:52             ` Eli Zaretskii

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=87o7m0p639.fsf@dsemy.com \
    --to=daniel@dsemy.com \
    --cc=emacs-devel@gnu.org \
    --cc=fitzsim@fitzsim.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.