TykaynJ'ai essayé de mettre un flux rss dans #elfeed, ça veut pas, le message d'erreur ne dit pas pourquoi. Qui a donc pondu ça sans le recouvrir ?
Daniel MendlerMy first commit to Elfeed happened on April 30, so about a month ago. Clearly the current burst of activity is coming to an end. It is time for Elfeed 4.0 soon.
https://github.com/emacs-elfeed/elfeed/commit/cfa931a0cf56e2e7be0ddadc41fcf11dc0209232
Elfeed 4.0 is going to be a big release.
In the last month there have been 448 commits by 17 developers, with 4499 additions and 2665 deletions. 175 issues have been closed and 18 PRs have been merged.
I plan to release a new version of Elfeed soon. Version 4.0.0 will include many fixes, functional improvements and new features. Please let us know if you have found issues that should be fixed.
The changelog:
https://github.com/emacs-elfeed/elfeed/blob/main/NEWS.org#upcoming-400-development
This is why free software maintenance sucks:
https://github.com/emacs-elfeed/elfeed/issues/614
This is the first thing I see today on the issue tracker. The code the user is worried about fits on two a4 pages, including the elfeed-dashboard.
But yes, we can just stop updating anything.
Daily Elfeed service post ;)
[error]: https://www.matem.unam.mx/~omar/apropos-emacs.xml: "HTTP 404"
Do you see a problem on your side? Server down?
Babys in a thundercloud 🏳⚧️ @ryan I use Org-mode with Elfeed-org so my feeds are declarative, and feeds belonging to subcategories inherit the parent properties. As a matter of fact, everything is in one big first-level section with a default :elfeed: keyword; if it isn’t tagged with the value of the relevant option, it isn’t treated by Elfeed.
So feeds look like this:
* Feeds :elfeed:
** English :en:
*** Pluralistic :pluralistic:
Here I try to aggregate a variety of forms of existence: e.g., underage people, undocumented people, Latinx people, etc.
**** [https://example.com/feed/][Campaign for the housing and education of underage and undocumented Black people, as per the law] :antiracism: :activism:
(…)
I try to keep the structure in a way so that I can easily recall it and navigate it, so it ought to be both semantic with as few sublevels and keywords as possible. Another option (not tested yet) is to do it as a literate document, as mentioned here:
https://gotosocial.social/@oceane/statuses/01KRR19NF7WS9TBF7SMB0NM6DG
Please note that literate programming documents don’t require the code blocks to follow the order of evaluation/execution/interpretation, as you generally write a build.sh file that will tangle the code blocks from a series of root code blocks. You then call every code block in the order of execution in the root code blocks, but they may be written following your natural language train of thought in any order, and either before or after the root blocks.
laotang@minad I will add my two cents as soon as I have some time. The short version: having all data directly in the filesystem also has some advantages - especially in terms of access and reliability. Performance issues and reliability of orgroam were often connected to sqlite. For the popular #Denote (and my rather unknown orgrr :) the absence of a database is a feature. I wonder what the main benefits of an sqlite #Elfeed are.
Thoughts on how to proceed with the Elfeed database: https://github.com/emacs-elfeed/elfeed/discussions/586
