Jorgen Schaefer <[EMAIL PROTECTED]> writes: > Yoni Rabkin Katzenell <[EMAIL PROTECTED]> writes: > >> Looking at emms-setup you can see that it needs updating. I guess that >> the first three levels: "minimalistic", "tiny" and "default" can stay >> exactly the same. >> >> The question is how to distribute the remaining functionality between >> "advanced" and "cvs". What is the policy here? Since the packages at >> this level have changed somewhat they need re-distribution. > > I would suggest the following four levels: > > `minimalistic' - My setup. Invisible playlist, just add and be happy. > `standard' - Playlist buffer, but no other modifications of the > mode line etc. > `fancy' - Everything we have in emms. Show-off.
Instead of `fancy' I suggest `all' since that describes what is going on. I know that you consider it fancy, but I consider it the norm. > `edge' - Same as fancy, except that here, new features are added > in the development version (to be moved to `fancy' on the next > release) Here I would go with `devel' since that explains more to the user than `edge'. I like the idea behind it though. > `custom' - A new type, which expects a list of things to use. I.e. > (emms-setup 'custom "~/snd/" '(playlist-mode info mode-line > streams lyrics playing-time)) > or so. To me `custom' sounds like a duplication of simply using `require' to add your own configuration. I doubt that people who are interested in fine-tuning Emms will use this since the Emacs environment does a lot to ease such customization. > But since I don't use emms-default.el, that's up to whoever does :-] I guess we will leave this for further comments and if no one argues or picks it up I'll take it on. > Btw, shouldn't emms-default.el be renamed to emms-setup.el? Definitely. I vote yes. -- "Cut your own wood and it will warm you twice" _______________________________________________ Emms-help mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emms-help
