The setter will now complain if the file to be added to `org-agenda-files' does
not exist and is not readable. It also now uses the proper functions from `org'
to update `org-agenda-files'.
This makes ‘db-helm’ obsolete again (already after one commit!). The function
to extract all files from ‘db/important-path’ has also been dropped in favor of
the standard ‘directory-files-recursively’. It’s not clear yet whether this
will also work on Windows, though.
Instead of giving a list, we now create the sources directly. This gives us the
possibility to configure certain aspects of the sources like matching behavior
and highlighting. Now we are much closer to the standard behavior of helm than
before.
Actually, we add the text properties ‘marker’ and ‘entry’ to the whole line, but
the alinging of the table somehow removes the text properties between two
columns. It is kept in the fields, though, and that is enough.
This is the main entry point to play automatically generated playlists (“auto
playlists”). It is using the value of ‘db/auto-playlist-file-function’ to
generate a list of files to play. This list if currently played using EMMS, via
‘db/-emms-playlist-from-files’.
Sometimes the string "Output of ‘…’" seems to be interpreted as directory name,
and then dired complains about it not being existent. It is not completely
understood yet when this will happen, and an easy workaround seems to be to
stick to a fixed string that works. This is what’s used now.
All music related functions that do not directly depend on EMMS will now go into
‘db/music’, with the intention that if we in the future replace EMMS with
something else, the API provided by ‘db/music’ will still be valid. This does
not mean, however, that functions in ‘db/music’ may not use functions from EMMS.
