"Husain Alshehhi" writes: > I have used nnrss before, and my issue with it is that it (1) > syncriounus, causing emacs to freeze for a while, (2) does not support > atom, and I have not used emacs 30, and (3) cannot be configured to use > curl, and that was necessary in my case since some website required > auth.
Joshua Barrett writes: > nnnrss is still synchronous like the rest of gnus, and does cause emacs to > freeze. I'd really like it and nnatom to be asynchronous, but I think that > would > require appreciably more work. I've enrolled all my feeds in the agent and > configured the demon to fetch only if emacs has been idle for some > time. However, both nnrss and nnnrss can be configured to use curl by setting > `mm-url-use-external` and `mm-url-program` accordingly, so that works at least Joshua Barrett writes: > I'd additionally note that you can use the agent to fetch mail in the > background > by invoking emacs in batch mode. It's suboptimal, but it does work. Daniel Semyonov writes: > I haven't had time to look at your code yet (so I don't know if you used > a similar method), but at least with nnatom you can use a local file as > the server address, which allows you to fetch a feed periodically > independently of Emacs, with nnatom only in charge of parsing the local > file. Daniel Semyonov writes: > It should be fairly simple to write a function which updates this file > asynchronously, and then triggers the synchronous parsing of it by Gnus > afterwards. Maybe you could try calling (info "(gnus) Child Gnusae") through (describe-package 'async), for the general case. (I don't use it myself: The most important part in the manual might very well be: "Exiting Gnus:: Stop reading news and get some work done" :-)) --
