elfeed-org VS melpa

3. For priority tracking, I use the builtin org-agenda with org-super-agenda[4] to create "views" based on some metadata[5].

This is all done without closing Emacs once.

[0]: https://github.com/remyhonig/elfeed-org

Not really. I use elfeed-org to manage my feeds in an ORG mode style. Some example (top reddit posts per month/week)

I am using elfeed-org, I do not understand what is wrong. I thought that the file elfeed,org containing all the feeds was the causem but it seems not, I have reduced it to 1 feed and it still shows the same error.

I maintain my feed list using the export feature of elfeed-org. I sync it manually by exporting to OPML and importing it into Nextcloud's web interface.

There are a lot of cool projects that build upon org-mode (org-export) being a static site generator like org-webring (which includes the ability of making a planet-style aggregator page) and elfeed-org.

I've tried the instalation guide from https://github.com/remyhonig/elfeed-org but it does not work:

By "db" you mean list of feeds? There are several way to accomplish this, first is by using elfeed-org and placing them in an org file and essentially copying said org file to another machine and run an elfeed-update

Watch the new pull requests to melpa: https://github.com/melpa/melpa/pulls

(require 'package) (add-to-list 'package-archives '("melpa" . "https://melpa.org/packages/") t) (package-initialize) (package-install 'use-package) (use-package exec-path-from-shell :ensure t :config (exec-path-from-shell-initialize)))

MELPA is definitely the biggest package archive, probably mostly on account of the lower barrier to entry compared to GNU ELPA (maybe the difference would have been less pronounced if NonGNU ELPA had been there from the beginning, but one can only speculate). MELPA has its own requirements for packages, but indeed copyright assignment to the FSF is not one of them.

I would suggest to start at reading the manual first. Then I would recommend reading the Melpa guidance, even if you do not plan to contribute your package to Melpa, since it contains very useful info about linting, writing your code etc.

The mxtoolbox link checks for SMTP blacklisting.. People won't be able to send mail from host with the IP address 178.128.185.1(which is the melpa.org webserver, not their mailserver, so everything's fine there).

Xah asked for his packages to be removed from MELPA a while back: https://github.com/melpa/melpa/issues/7755

Observe that package.el compile files when they are installed, and they are not compiled in any particular order (actually whatever directory-files returns, which is what OS returns). So if you have multiple files that depend on each other, it is something to think of. There are also some guidelines on how to structure your project on Melpa.