Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit

Elfeed has the ability to retrieve urls from gopher and the local file
system too, however elfeed-org would just ignore those links.

Git stats


Failed to load latest commit information.
Latest commit message
Commit time


Configure the Elfeed RSS reader with an Orgmode file


Maintaining tags for all my rss feeds is cumbersome using the regular flat list where there is no hierarchy and tag names are duplicated a lot. For example this is how elfeed users typically configure their subscriptions.

(defvar elfeed-feeds-alist
  '(("" blog math)
    ("" blog dev)
    ("" blog)
    ("" comic)
    ("" image math)
    ("" comic)
    ("" blog dev)
    ("" comic)
    ("" blog dev)
    ("" blog)
    ("" comic)
    ("" blog dev)))

If you want to add a custom title to a feed, that is even more cumbersome...


Org-mode makes the book keeping of tags and feeds much easier. Tags get inherited from parent headlines so there is no need to specify tags for each and every feed.

* Blogs                                                              :elfeed:
** entry-title: \(linux\|linus\|ubuntu\|kde\|gnome\)                  :linux:
** :mustread:
** [[][Org Mode Links supported as well]]
** Software Development                                                 :dev:
*** Emacs                                                    :emacs:mustread:
**** entry-title: \(emacs\|org-mode\)
**** [[toobnix:154][EmacsConf]]
*** Web Development                                                     :web:
*** Eclipse                                                         :eclipse:
     A description of a feed can be written under any headline.
     The text will be ignored by elfeed.
****                         :ignore:
****                             :video:
#+link toobnix

Some highlights:

  • [[][Org Mode Links supported as well]] If you choose to use org-mode links, the link description will be used as the feed's title in Elfeed. This is useful for feeds with long titles.
  • entry-title: \(emacs\|org-mode\) Tags any blog post with "emacs" or "org-mode" in the title according to it's given and inherited tags (in the example above "emacs", "mustread" and "dev").
  • :ignore: The "ignore" excludes the feed completely from your checked subscriptions. You can use another name for "ignore" by customizing rmh-elfeed-org-ignore-tag. These "ignore" tags are set by elfeed-org automatically on feed errors (wrong urls or renamed feeds for example) if rmh-elfeed-org-auto-ignore-invalid-feeds is set to t.

Import/Export OPML

Use elfeed-org-export-opml to export the tree structure of feeds to OPML format to a temporary buffer. This will allow you to make edits before saving it. You will probabably want to do this because most readers don't allow more than 2 levels while elfeed-org has no limit.

Use elfeed-org-import-opml to import an OPML file to an elfeed-org structured tree.

The Configuration Tree

You can use multiple trees. Those trees can be in same file or spread across multiple files specified in the list rmh-elfeed-org-files. Why would I want to use multiple trees? You can have a tree in a file that you may want to share with your emacs.d on GitHub and keep your personal feeds in a separate private repository.

In the initial version of this package the tree is identified by setting the ID property to to the value of rmh-elfeed-org-tree-id ("elfeed" by default) but that property turns out to be special (see the org mode manual) and I should not have used it. To not break any existing users' configurations this is still allowed but I recommend to tag the tree now with the value of rmh-elfeed-org-tree-id.

So instead of

* Blogs
 :ID: elfeed

I recommend to use

* Blogs                                                              :elfeed:


A few tips for the org-mode feed configuration:

  • The tree should have a tag matching the string specified in the variable rmh-elfeed-org-tree-id.
  • Feeds must start with http, or be in org-mode link format (the URL should still start with http).
  • Tag rules must start with entry-title: and end with a regular expression.
  • A tag rule tags all the posts that match the regular expression in the title using a "tag hook" with elfeed-make-tagger. For more info see
  • You may add text below the headline with the url to describe the feed or to add notes. They will be ignored.
  • Headlines not starting with http or entry-title: will be ignored.



Runs on emacs versions specified in .github/workflows/ci.yml

This package needs org-mode 8.2.7 to run properly if you use the emacs-24 distribution. The reason that that org-mode version is needed is because org-mode 8.2.6 - at least in combination with GNU Emacs - causes the error (error "recenter'ing a window that does not display current-buffer.").

The minimum version of org-mode that is minimally needed to even run is org-mode 8.1 as that is the first release that defined the function org-element-map which is critical for this package.


Built with Spacemacs

This package is part of the excellent Spacemacs. See Elfeed Layer Documentation for installation instructions.

Through MELPA


;; Install through package manager
M-x package-install <ENTER>
elfeed-org <ENTER>


Download elfeed-org

cd ~/.emacs.d/lisp

Install the package in Emacs

C-x C-f ~/.emacs.d/lisp/elfeed-org.el <ENTER>
M-x package-install-from-buffer <ENTER>


In your initialization script add the following:

;; Load elfeed-org
(require 'elfeed-org)

;; Initialize elfeed-org
;; This hooks up elfeed-org to read the configuration when elfeed
;; is started with =M-x elfeed=

;; Optionally specify a number of files containing elfeed
;; configuration. If not set then the location below is used.
;; Note: The customize interface is also supported.
(setq rmh-elfeed-org-files (list "~/.emacs.d/"))

Feature requests and bug fixes

I appreciate feature requests and code snippets provided to fix things, but I really don't have much spare time nowadays. If you'd like to add a feature or fix a bug, please post a pull requests and I will merge it right away if has a corresponding test and an update of the README if applicable. I just migrated the CI from Travis - which was not functional anymore - to Github Action so this should be a faster process now. And to close off: a big thank you to all PR authors and issue submitters!