Yoni Rabkin
2015-12-10 21:51:14 UTC
Emms currently has a unique configuration system. You require
`emms-setup' feature and then call one of the configuration levels, such
as (emms-all). This was originally envisioned as a setup where the
developers of the individual Emms packages would begin by placing their
code in the emms-devel configuration and then migrate them to emms-all
as the code matured. However, nobody really does this.
My plan is to merge the `emms-all', `emms-devel' and `emms-standard'
configuration levels so that they all load
everything. `emms-minimalistic' will remain the same.
The manual will advise to call `emms-all' and won't mention `emms-devel'
and `emms-standard'.
This shouldn't break anyone's existing setup.
`emms-setup' feature and then call one of the configuration levels, such
as (emms-all). This was originally envisioned as a setup where the
developers of the individual Emms packages would begin by placing their
code in the emms-devel configuration and then migrate them to emms-all
as the code matured. However, nobody really does this.
My plan is to merge the `emms-all', `emms-devel' and `emms-standard'
configuration levels so that they all load
everything. `emms-minimalistic' will remain the same.
The manual will advise to call `emms-all' and won't mention `emms-devel'
and `emms-standard'.
This shouldn't break anyone's existing setup.
--
"Cut your own wood and it will warm you twice"
"Cut your own wood and it will warm you twice"