GNU bug report logs -
#66188
29.1; Include Atom feed reader
Previous Next
Reported by: Daniel Cerqueira <dan.list <at> brilhante.top>
Date: Mon, 25 Sep 2023 07:15:02 UTC
Severity: wishlist
Tags: patch
Merged with 64202
Found in version 29.1
Done: Eric Abrahamsen <eric <at> ericabrahamsen.net>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 66188 in the body.
You can then email your comments to 66188 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Mon, 25 Sep 2023 07:15:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Daniel Cerqueira <dan.list <at> brilhante.top>:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org.
(Mon, 25 Sep 2023 07:15:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Gnus has support to read RSS feeds. Can you guys add support to also
read Atom feeds in Gnus?
May import some code from elfeed.el on this year's Hackoberfest?
Thanks :-)
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Mon, 25 Sep 2023 09:23:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 66188 <at> debbugs.gnu.org (full text, mbox):
forcemerge 64202 66188
thanks
Daniel Cerqueira <dan.list <at> brilhante.top> writes:
> Gnus has support to read RSS feeds. Can you guys add support to also
> read Atom feeds in Gnus?
>
> May import some code from elfeed.el on this year's Hackoberfest?
>
> Thanks :-)
This is a duplicate of Bug#64202, so I'm merging them.
Forcibly Merged 64202 66188.
Request was from
Stefan Kangas <stefankangas <at> gmail.com>
to
control <at> debbugs.gnu.org.
(Mon, 25 Sep 2023 09:32:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Wed, 07 Feb 2024 17:58:02 GMT)
Full text and
rfc822 format available.
Message #13 received at 66188 <at> debbugs.gnu.org (full text, mbox):
>>>>> Daniel Semyonov writes:
> I the issue is that your locale's "preferred clock" is a 12 hour
> clock and I didn't realize that I need to also add "%p" to the
> format string to show the locale's version of "AM" or "PM" (or
> nothing).
> I'll push a fix soon.
I've pushed a commit which turns the displayed date format into a user
option (and fixes the default value, and uses a simple date format when
it isn't displayed).
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Mon, 18 Mar 2024 17:00:03 GMT)
Full text and
rfc822 format available.
Message #16 received at 66188 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I pushed a few more commits (an updated patch is attached) which fix
some edge cases with ephemeral groups and simplify some functions.
Daniel
[0001-Gnus-Add-back-end-for-Atom-feeds-nnatom.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Sun, 24 Mar 2024 13:38:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 66188 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
>>>>> Daniel Semyonov writes:
> I pushed a few more commits (an updated patch is attached) which fix
> some edge cases with ephemeral groups and simplify some functions.
And a few more which fix a typo which caused duplicate groups being
created after renaming a group and relaunching Gnus, and fix the "Web
Feed Back Ends" subsection in the Gnus manual by making it a
subsubsection. Updated patch attached.
Daniel
[0001-Gnus-Add-back-end-for-Atom-feeds-nnatom.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Sat, 06 Apr 2024 09:02:05 GMT)
Full text and
rfc822 format available.
Message #22 received at 66188 <at> debbugs.gnu.org (full text, mbox):
Ping! Eric, any comments about this? Should we install this?
> Cc: Eric Abrahamsen <eric <at> ericabrahamsen.net>, 66188 <at> debbugs.gnu.org,
> 64202 <at> debbugs.gnu.org
> Date: Sun, 24 Mar 2024 15:35:18 +0200
> From: Daniel Semyonov via "Bug reports for GNU Emacs,
> the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
>
> >>>>> Daniel Semyonov writes:
>
> > I pushed a few more commits (an updated patch is attached) which fix
> > some edge cases with ephemeral groups and simplify some functions.
>
> And a few more which fix a typo which caused duplicate groups being
> created after renaming a group and relaunching Gnus, and fix the "Web
> Feed Back Ends" subsection in the Gnus manual by making it a
> subsubsection. Updated patch attached.
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Thu, 18 Apr 2024 09:03:04 GMT)
Full text and
rfc822 format available.
Message #25 received at 66188 <at> debbugs.gnu.org (full text, mbox):
Ping! Ping! Eric, any comments?
> Cc: 66188 <at> debbugs.gnu.org, 64202 <at> debbugs.gnu.org, jimjoe <at> gmx.net
> Date: Sat, 06 Apr 2024 12:01:19 +0300
> From: Eli Zaretskii <eliz <at> gnu.org>
>
> Ping! Eric, any comments about this? Should we install this?
>
> > Cc: Eric Abrahamsen <eric <at> ericabrahamsen.net>, 66188 <at> debbugs.gnu.org,
> > 64202 <at> debbugs.gnu.org
> > Date: Sun, 24 Mar 2024 15:35:18 +0200
> > From: Daniel Semyonov via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" <bug-gnu-emacs <at> gnu.org>
> >
> > >>>>> Daniel Semyonov writes:
> >
> > > I pushed a few more commits (an updated patch is attached) which fix
> > > some edge cases with ephemeral groups and simplify some functions.
> >
> > And a few more which fix a typo which caused duplicate groups being
> > created after renaming a group and relaunching Gnus, and fix the "Web
> > Feed Back Ends" subsection in the Gnus manual by making it a
> > subsubsection. Updated patch attached.
>
>
>
>
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Sun, 21 Apr 2024 00:48:03 GMT)
Full text and
rfc822 format available.
Message #28 received at 66188 <at> debbugs.gnu.org (full text, mbox):
Eli Zaretskii <eliz <at> gnu.org> writes:
> Ping! Ping! Eric, any comments?
Yes, let's do it! My only comment right now is that the manual should
explicitly list the steps for creating an atom group: "B nnatom RET" and
insert URL without protocol. I still have dreams of fixing the group
creation code to prompt for the address, but that can wait.
Daniel, would you make that addition? Do you have push access to the
Emacs repo?
Eric
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Sun, 21 Apr 2024 18:44:16 GMT)
Full text and
rfc822 format available.
Message #31 received at 66188 <at> debbugs.gnu.org (full text, mbox):
>>>>> Eric Abrahamsen writes:
> Eli Zaretskii <eliz <at> gnu.org> writes:
>> Ping! Ping! Eric, any comments?
> Yes, let's do it! My only comment right now is that the manual should
> explicitly list the steps for creating an atom group: "B nnatom RET" and
> insert URL without protocol. I still have dreams of fixing the group
> creation code to prompt for the address, but that can wait.
> Daniel, would you make that addition?
Does the following text (in the 'Atom' subsection of the Gnus manual)
not suffice?
The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
Gnus servers (with a single group), as you would with any other method,
by supplying the location of the feed as the server address. Note,
however, that the server address shouldn't be prefixed with <http://> or
<https://>.
> Do you have push access to the Emacs repo?
I do not.
Daniel
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Mon, 22 Apr 2024 03:12:04 GMT)
Full text and
rfc822 format available.
Message #34 received at 66188 <at> debbugs.gnu.org (full text, mbox):
On 04/21/24 21:41 PM, Daniel Semyonov wrote:
>>>>>> Eric Abrahamsen writes:
>
> > Eli Zaretskii <eliz <at> gnu.org> writes:
> >> Ping! Ping! Eric, any comments?
>
> > Yes, let's do it! My only comment right now is that the manual should
> > explicitly list the steps for creating an atom group: "B nnatom RET" and
> > insert URL without protocol. I still have dreams of fixing the group
> > creation code to prompt for the address, but that can wait.
>
> > Daniel, would you make that addition?
>
> Does the following text (in the 'Atom' subsection of the Gnus manual)
> not suffice?
>
> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
> Gnus servers (with a single group), as you would with any other method,
> by supplying the location of the feed as the server address. Note,
> however, that the server address shouldn't be prefixed with <http://> or
> <https://>.
I think we need to at least make it clear that you can't create these
groups with "G m", which to me anyway is the "normal" way of making a
group. It wouldn't hurt to be more explicit about the fact that feeds
are created at the server level, not the group level. I'm not suggesting
anything radical, something like:
--8<---------------cut here---------------start------------->8---
The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as Gnus
servers, in your Gnus init files or as foreign servers via "B" in the
*Group* buffer. The feed location is supplied as the server address, and
each server only contains a single group. Note, however, that the server
address shouldn't be prefixed with <http://> or <https://>.
--8<---------------cut here---------------end--------------->8---
Or something like that. WDYT?
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Mon, 22 Apr 2024 22:47:02 GMT)
Full text and
rfc822 format available.
Message #37 received at 66188 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
>>>>> Eric Abrahamsen writes:
> On 04/21/24 21:41 PM, Daniel Semyonov wrote:
>>>>>>> Eric Abrahamsen writes:
>>
>> > Eli Zaretskii <eliz <at> gnu.org> writes:
>> >> Ping! Ping! Eric, any comments?
>>
>> > Yes, let's do it! My only comment right now is that the manual should
>> > explicitly list the steps for creating an atom group: "B nnatom RET" and
>> > insert URL without protocol. I still have dreams of fixing the group
>> > creation code to prompt for the address, but that can wait.
>>
>> > Daniel, would you make that addition?
>>
>> Does the following text (in the 'Atom' subsection of the Gnus manual)
>> not suffice?
>>
>> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
>> Gnus servers (with a single group), as you would with any other method,
>> by supplying the location of the feed as the server address. Note,
>> however, that the server address shouldn't be prefixed with <http://> or
>> <https://>.
> I think we need to at least make it clear that you can't create these
> groups with "G m", which to me anyway is the "normal" way of making a
> group. It wouldn't hurt to be more explicit about the fact that feeds
> are created at the server level, not the group level. I'm not suggesting
> anything radical, something like:
> --8<---------------cut here---------------start------------->8---
> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as Gnus
> servers, in your Gnus init files or as foreign servers via "B" in the
> *Group* buffer. The feed location is supplied as the server address, and
> each server only contains a single group. Note, however, that the server
> address shouldn't be prefixed with <http://> or <https://>.
> --8<---------------cut here---------------end--------------->8---
> Or something like that. WDYT?
I gave it another thought and you're right, it should be more explicit.
I've attached an updated patch but here's the new version of the
paragraph (since I actually ended up being even more explicit):
The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
Gnus servers, by adding them to ‘gnus-secondary-select-methods’ or as
foreign servers by pressing "B" in the ‘*Group*’ buffer, for example
(*note Finding the News). The address of each server is its feed's
location (though the address shouldn't be prefixed with <http://> or
<https://>) and each server contains a single group which holds the
feed's entries.
Daniel
[0001-Gnus-Add-back-end-for-Atom-feeds-nnatom.patch (text/x-patch, attachment)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Tue, 23 Apr 2024 14:36:05 GMT)
Full text and
rfc822 format available.
Message #40 received at 66188 <at> debbugs.gnu.org (full text, mbox):
On 04/23/24 01:44 AM, Daniel Semyonov wrote:
>>>>>> Eric Abrahamsen writes:
>
> > On 04/21/24 21:41 PM, Daniel Semyonov wrote:
> >>>>>>> Eric Abrahamsen writes:
> >>
> >> > Eli Zaretskii <eliz <at> gnu.org> writes:
> >> >> Ping! Ping! Eric, any comments?
> >>
> >> > Yes, let's do it! My only comment right now is that the manual should
> >> > explicitly list the steps for creating an atom group: "B nnatom RET" and
> >> > insert URL without protocol. I still have dreams of fixing the group
> >> > creation code to prompt for the address, but that can wait.
> >>
> >> > Daniel, would you make that addition?
> >>
> >> Does the following text (in the 'Atom' subsection of the Gnus manual)
> >> not suffice?
> >>
> >> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
> >> Gnus servers (with a single group), as you would with any other method,
> >> by supplying the location of the feed as the server address. Note,
> >> however, that the server address shouldn't be prefixed with <http://> or
> >> <https://>.
>
> > I think we need to at least make it clear that you can't create these
> > groups with "G m", which to me anyway is the "normal" way of making a
> > group. It wouldn't hurt to be more explicit about the fact that feeds
> > are created at the server level, not the group level. I'm not suggesting
> > anything radical, something like:
>
> > --8<---------------cut here---------------start------------->8---
> > The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as Gnus
> > servers, in your Gnus init files or as foreign servers via "B" in the
> > *Group* buffer. The feed location is supplied as the server address, and
> > each server only contains a single group. Note, however, that the server
> > address shouldn't be prefixed with <http://> or <https://>.
> > --8<---------------cut here---------------end--------------->8---
>
> > Or something like that. WDYT?
>
> I gave it another thought and you're right, it should be more explicit.
> I've attached an updated patch but here's the new version of the
> paragraph (since I actually ended up being even more explicit):
>
> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
> Gnus servers, by adding them to ‘gnus-secondary-select-methods’ or as
> foreign servers by pressing "B" in the ‘*Group*’ buffer, for example
> (*note Finding the News). The address of each server is its feed's
> location (though the address shouldn't be prefixed with <http://> or
> <https://>) and each server contains a single group which holds the
> feed's entries.
That looks great -- I think it can't hurt to provide some more
hand-holding in the manual. I'll get this in this morning.
Thanks!
Eric
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Tue, 23 Apr 2024 22:10:07 GMT)
Full text and
rfc822 format available.
Message #43 received at 66188 <at> debbugs.gnu.org (full text, mbox):
>>>>> Eric Abrahamsen writes:
> On 04/23/24 01:44 AM, Daniel Semyonov wrote:
>>>>>>> Eric Abrahamsen writes:
>>
>> > On 04/21/24 21:41 PM, Daniel Semyonov wrote:
>> >>>>>>> Eric Abrahamsen writes:
>> >>
>> >> > Eli Zaretskii <eliz <at> gnu.org> writes:
>> >> >> Ping! Ping! Eric, any comments?
>> >>
>> >> > Yes, let's do it! My only comment right now is that the manual should
>> >> > explicitly list the steps for creating an atom group: "B nnatom RET" and
>> >> > insert URL without protocol. I still have dreams of fixing the group
>> >> > creation code to prompt for the address, but that can wait.
>> >>
>> >> > Daniel, would you make that addition?
>> >>
>> >> Does the following text (in the 'Atom' subsection of the Gnus manual)
>> >> not suffice?
>> >>
>> >> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
>> >> Gnus servers (with a single group), as you would with any other method,
>> >> by supplying the location of the feed as the server address. Note,
>> >> however, that the server address shouldn't be prefixed with <http://> or
>> >> <https://>.
>>
>> > I think we need to at least make it clear that you can't create these
>> > groups with "G m", which to me anyway is the "normal" way of making a
>> > group. It wouldn't hurt to be more explicit about the fact that feeds
>> > are created at the server level, not the group level. I'm not suggesting
>> > anything radical, something like:
>>
>> > --8<---------------cut here---------------start------------->8---
>> > The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as Gnus
>> > servers, in your Gnus init files or as foreign servers via "B" in the
>> > *Group* buffer. The feed location is supplied as the server address, and
>> > each server only contains a single group. Note, however, that the server
>> > address shouldn't be prefixed with <http://> or <https://>.
>> > --8<---------------cut here---------------end--------------->8---
>>
>> > Or something like that. WDYT?
>>
>> I gave it another thought and you're right, it should be more explicit.
>> I've attached an updated patch but here's the new version of the
>> paragraph (since I actually ended up being even more explicit):
>>
>> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
>> Gnus servers, by adding them to ‘gnus-secondary-select-methods’ or as
>> foreign servers by pressing "B" in the ‘*Group*’ buffer, for example
>> (*note Finding the News). The address of each server is its feed's
>> location (though the address shouldn't be prefixed with <http://> or
>> <https://>) and each server contains a single group which holds the
>> feed's entries.
> That looks great -- I think it can't hurt to provide some more
> hand-holding in the manual. I'll get this in this morning.
Great, I just did a git pull and I see it; thank you very much!
Daniel
(BTW I guess this report should be closed; I'm not really sure what the
procedure is since this technically isn't my report, but instead was
merged with mine at some point)
Information forwarded
to
bug-gnu-emacs <at> gnu.org, bugs <at> gnus.org:
bug#66188; Package
emacs,gnus.
(Wed, 24 Apr 2024 14:23:05 GMT)
Full text and
rfc822 format available.
Message #46 received at 66188-done <at> debbugs.gnu.org (full text, mbox):
On 04/24/24 01:07 AM, Daniel Semyonov wrote:
>>>>>> Eric Abrahamsen writes:
>
> > On 04/23/24 01:44 AM, Daniel Semyonov wrote:
> >>>>>>> Eric Abrahamsen writes:
> >>
> >> > On 04/21/24 21:41 PM, Daniel Semyonov wrote:
> >> >>>>>>> Eric Abrahamsen writes:
> >> >>
> >> >> > Eli Zaretskii <eliz <at> gnu.org> writes:
> >> >> >> Ping! Ping! Eric, any comments?
> >> >>
> >> >> > Yes, let's do it! My only comment right now is that the manual should
> >> >> > explicitly list the steps for creating an atom group: "B nnatom RET" and
> >> >> > insert URL without protocol. I still have dreams of fixing the group
> >> >> > creation code to prompt for the address, but that can wait.
> >> >>
> >> >> > Daniel, would you make that addition?
> >> >>
> >> >> Does the following text (in the 'Atom' subsection of the Gnus manual)
> >> >> not suffice?
> >> >>
> >> >> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
> >> >> Gnus servers (with a single group), as you would with any other method,
> >> >> by supplying the location of the feed as the server address. Note,
> >> >> however, that the server address shouldn't be prefixed with <http://> or
> >> >> <https://>.
> >>
> >> > I think we need to at least make it clear that you can't create these
> >> > groups with "G m", which to me anyway is the "normal" way of making a
> >> > group. It wouldn't hurt to be more explicit about the fact that feeds
> >> > are created at the server level, not the group level. I'm not suggesting
> >> > anything radical, something like:
> >>
> >> > --8<---------------cut here---------------start------------->8---
> >> > The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as Gnus
> >> > servers, in your Gnus init files or as foreign servers via "B" in the
> >> > *Group* buffer. The feed location is supplied as the server address, and
> >> > each server only contains a single group. Note, however, that the server
> >> > address shouldn't be prefixed with <http://> or <https://>.
> >> > --8<---------------cut here---------------end--------------->8---
> >>
> >> > Or something like that. WDYT?
> >>
> >> I gave it another thought and you're right, it should be more explicit.
> >> I've attached an updated patch but here's the new version of the
> >> paragraph (since I actually ended up being even more explicit):
> >>
> >> The ‘nnatom’ back end allows you to add HTTP or local Atom feeds as
> >> Gnus servers, by adding them to ‘gnus-secondary-select-methods’ or as
> >> foreign servers by pressing "B" in the ‘*Group*’ buffer, for example
> >> (*note Finding the News). The address of each server is its feed's
> >> location (though the address shouldn't be prefixed with <http://> or
> >> <https://>) and each server contains a single group which holds the
> >> feed's entries.
>
> > That looks great -- I think it can't hurt to provide some more
> > hand-holding in the manual. I'll get this in this morning.
>
> Great, I just did a git pull and I see it; thank you very much!
>
> Daniel
>
> (BTW I guess this report should be closed; I'm not really sure what the
> procedure is since this technically isn't my report, but instead was
> merged with mine at some point)
Yes, we can close these, if they've been merged then they're the "same"
report. And bug reports aren't precious, if we need another, we can open
another!
Speaking of getting more bug reports, do you want to post on
gnus.general and let people know this new backend is available? It would
be good to get some usage.
Thanks,
Eric
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org.
(Thu, 23 May 2024 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 353 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.