Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.emacs.gnus > #7877 > unrolled thread

ATOM Feeds in Gnus

Started byJonathan Lamothe <jonathan@jlamothe.net>
First post2026-04-15 13:59 -0400
Last post2026-04-16 18:48 -0400
Articles 8 — 4 participants

Back to article view | Back to gnu.emacs.gnus


Contents

  ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-15 13:59 -0400
    Re: ATOM Feeds in Gnus Mekeor Melire <mekeor@posteo.de> - 2026-04-15 21:14 +0200
      Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-15 18:17 -0400
        Re: ATOM Feeds in Gnus Thomas DUPOND <thomas@dupond.eu> - 2026-04-16 09:05 +0200
          Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-16 14:32 -0400
            Re: ATOM Feeds in Gnus Thomas DUPOND <thomas@dupond.eu> - 2026-04-17 09:23 +0200
              Compiling GNU Emacs from source (was: ATOM Feeds in Gnus) Daniel Cerqueira <dan.list@lispclub.com> - 2026-07-16 11:19 +0100
    Re: ATOM Feeds in Gnus Jonathan Lamothe <jonathan@jlamothe.net> - 2026-04-16 18:48 -0400

#7877 — ATOM Feeds in Gnus

FromJonathan Lamothe <jonathan@jlamothe.net>
Date2026-04-15 13:59 -0400
SubjectATOM Feeds in Gnus
Message-ID<87340wje9c.fsf@posteo.de>
Hi all,

I've recently started using Gnus for all my usenet/mail/RSS needs.  The
only issue I'm running into is that I can't seem to subscribe to ATOM
feeds (RSS feeds work fine).  It seems the nnatom backend is missing.
Is there something special I need to do to add it?

-- 
Regards,
Jonathan Lamothe
https://jlamothe.net

[toc] | [next] | [standalone]


#7878

FromMekeor Melire <mekeor@posteo.de>
Date2026-04-15 21:14 +0200
Message-ID<877bq83uk7.fsf@posteo.de>
In reply to#7877
On 2026-04-15 at 13:59, <jonathan@jlamothe.net> wrote:

> It seems the nnatom backend is missing.

Did you try evaluating (require 'nnatom)? The corresponding file
is located at lisp/gnus/nnatom.el in GNU Emacs repository and
might be located at /usr/share/emacs/30.2/lisp/gnus/nnatom.el.gz
or similar on your file system.

[toc] | [prev] | [next] | [standalone]


#7879

FromJonathan Lamothe <jonathan@jlamothe.net>
Date2026-04-15 18:17 -0400
Message-ID<87ldenj2b5.fsf@posteo.de>
In reply to#7878
Mekeor Melire <mekeor@posteo.de> writes:

> On 2026-04-15 at 13:59, <jonathan@jlamothe.net> wrote:
>
>> It seems the nnatom backend is missing.
>
> Did you try evaluating (require 'nnatom)? The corresponding file
> is located at lisp/gnus/nnatom.el in GNU Emacs repository and
> might be located at /usr/share/emacs/30.2/lisp/gnus/nnatom.el.gz
> or similar on your file system.

Debugger entered--Lisp error: (file-missing "Cannot open load file" "No
such file or directory" "nnatom")

Seems it doean't exist?  Or at least doesn't live in a path that my
Emacs knows about.

-- 
Regards,
Jonathan Lamothe
https://jlamothe.net

[toc] | [prev] | [next] | [standalone]


#7880

FromThomas DUPOND <thomas@dupond.eu>
Date2026-04-16 09:05 +0200
Message-ID<cT%DR.52686$YhJ7.11579@fx02.ams4>
In reply to#7879
Le 2026-04-16 à 00:17, Jonathan Lamothe a écrit :
> Mekeor Melire <mekeor@posteo.de> writes:
> 
>> On 2026-04-15 at 13:59, <jonathan@jlamothe.net> wrote:
>>
>>> It seems the nnatom backend is missing.
>>
>> Did you try evaluating (require 'nnatom)? The corresponding file
>> is located at lisp/gnus/nnatom.el in GNU Emacs repository and
>> might be located at /usr/share/emacs/30.2/lisp/gnus/nnatom.el.gz
>> or similar on your file system.
> 
> Debugger entered--Lisp error: (file-missing "Cannot open load file" "No
> such file or directory" "nnatom")
> 
> Seems it doean't exist?  Or at least doesn't live in a path that my
> Emacs knows about.

Are you on a Debian based distro?  I myself am using Debian Bookworm and 
I only have emacs version 28.2 from 2022 which does not include nnatom, 
written in 2023.

I should upgrade to Debian Trixie which comes with emacs 30.1 and 
includes nnatom.el.

Best,
-- 
Thomas

[toc] | [prev] | [next] | [standalone]


#7881

FromJonathan Lamothe <jonathan@jlamothe.net>
Date2026-04-16 14:32 -0400
Message-ID<87340ug3iu.fsf@posteo.de>
In reply to#7880
Thomas DUPOND <thomas@dupond.eu> writes:

> Are you on a Debian based distro?  I myself am using Debian Bookworm
> and I only have emacs version 28.2 from 2022 which does not include
> nnatom, written in 2023.
>
> I should upgrade to Debian Trixie which comes with emacs 30.1 and
> includes nnatom.el.

Yeah, I'm still on Debian 12.  I keep putting off the upgrades because
something invariably breaks and that gives me anxiety.  I also have a
Nextcloud server that's complaining about an outdated version of PHP, so
that's another reason I need to get on with it.

-- 
Regards,
Jonathan Lamothe
https://jlamothe.net

[toc] | [prev] | [next] | [standalone]


#7883

FromThomas DUPOND <thomas@dupond.eu>
Date2026-04-17 09:23 +0200
Message-ID<ZdlER.118943$K_va.51653@fx16.ams4>
In reply to#7881
Le 2026-04-16 à 20:32, Jonathan Lamothe a écrit :
> Thomas DUPOND <thomas@dupond.eu> writes:
> 
>> Are you on a Debian based distro?  I myself am using Debian Bookworm
>> and I only have emacs version 28.2 from 2022 which does not include
>> nnatom, written in 2023.
>>
>> I should upgrade to Debian Trixie which comes with emacs 30.1 and
>> includes nnatom.el.
> 
> Yeah, I'm still on Debian 12.  I keep putting off the upgrades because
> something invariably breaks and that gives me anxiety.  I also have a
> Nextcloud server that's complaining about an outdated version of PHP, so
> that's another reason I need to get on with it.
> 

I understand, I did it yesterday and it took me a while even with the 
official documentation.

 From what I understand now having been through it, the steps I should 
have taken were:

1. Update to the latest bookworm release with `apt update` and `apt 
full-upgrade`
2. Removing old packages with `apt autoremove`
3. Switch over to trixie repositories in a new apt source file in 
/etc/apt/sources.list.d/debian.sources (see 
https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#adding-apt-internet-sources)
4. Remove old source files (for me /etc/apt/sources.list)
5. `apt update`
6. `apt upgrade --without-new-pkgs`
7. `apt full-upgrade`

Which is not too complicated but somehow I got lost in the many links 
available in the official documentation and ended up only half upgrading 
my system because my apt sources file was not correct (I should have 
just copy-pasted the one I linked in step 3.

This was quite convoluted for my installation with no personal packages 
nor packages from third parties, a "pure" Debian install as they say.

Good luck!
-- 
Thomas

[toc] | [prev] | [next] | [standalone]


#7888 — Compiling GNU Emacs from source (was: ATOM Feeds in Gnus)

FromDaniel Cerqueira <dan.list@lispclub.com>
Date2026-07-16 11:19 +0100
SubjectCompiling GNU Emacs from source (was: ATOM Feeds in Gnus)
Message-ID<87pl0n5j90.fsf_-_@lispclub.com>
In reply to#7883

[Multipart message — attachments visible in raw view] — view raw

Thomas DUPOND <thomas@dupond.eu> writes:

[...]

> From what I understand now having been through it, the steps I should
> have taken were:
>
> 1. Update to the latest bookworm release with `apt update` and `apt
> full-upgrade`
> 2. Removing old packages with `apt autoremove`
> 3. Switch over to trixie repositories in a new apt source file in
> /etc/apt/sources.list.d/debian.sources (see
> https://www.debian.org/releases/trixie/release-notes/upgrading.en.html#adding-apt-internet-sources)
> 4. Remove old source files (for me /etc/apt/sources.list)
> 5. `apt update`
> 6. `apt upgrade --without-new-pkgs`
> 7. `apt full-upgrade`
>
> Which is not too complicated but somehow I got lost in the many links
> available in the official documentation and ended up only half
> upgrading my system because my apt sources file was not correct (I
> should have just copy-pasted the one I linked in step 3.

[...]

This is a case, where it is useful to know how to compile GNU Emacs from
source.  With knowing this, you don't need a full distro update in order
to just get the latest GNU Emacs.  And you can also get to have multiple
GNU Emacs versions on the same system ;-) .  Due to GNU Emacs
friendliness towards the system, and towards the user, when it installs.

It is as easy as downloading the latest tarball of GNU Emacs, extracting
the tarball and `cd` into it, then run -- one step at the time --
`./configure && make && sudo make install`.

Compiling GNU packages is quite straightforward, the method I explained
also applies to most of GNU packages.

Hope this can help you.  And if you are stuck somewhere in this process,
do communicate here...  I can try helping you (although I am not very
proficient at C compiling).


Cheers for Freedom,

-- 
A little Consideration, a little Thought for Others, makes
all the difference. ~ Alan Alexander Milne

[toc] | [prev] | [next] | [standalone]


#7882

FromJonathan Lamothe <jonathan@jlamothe.net>
Date2026-04-16 18:48 -0400
Message-ID<871pgeed32.fsf@posteo.de>
In reply to#7877
Jonathan Lamothe <jonathan@jlamothe.net> writes:

> Hi all,
>
> I've recently started using Gnus for all my usenet/mail/RSS needs.  The
> only issue I'm running into is that I can't seem to subscribe to ATOM
> feeds (RSS feeds work fine).  It seems the nnatom backend is missing.
> Is there something special I need to do to add it?

So the problem seems to be the fact that I'm using Emacs from the
default repository on Debian 12, which doesn't include the nnatom
backend.  I'm told that upgrading to Debian 13 will resolve the issue.
I've just been putting the upgrade off because every time I do,
something breaks.

-- 
Regards,
Jonathan Lamothe
https://jlamothe.net

[toc] | [prev] | [standalone]


Back to top | Article view | gnu.emacs.gnus


csiph-web