unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Björn Bidar" <bjorn.bidar@thaodan.de>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: best practices for implementing Emms configuration
Date: Sat, 10 Dec 2022 02:10:01 +0200	[thread overview]
Message-ID: <87sfhoyv8m.fsf@thaodan.de> (raw)
In-Reply-To: <87pmcspi77.fsf@rabkins.net> (Yoni Rabkin's message of "Fri, 09 Dec 2022 13:04:12 -0500")

Yoni Rabkin <yoni@rabkins.net> writes:

> Hello all,
>
> We are trying to make Emms (https://www.gnu.org/software/emms/) better
> out of the box.
>
> The idea is to have the user invoke "M-x emms-setup", have Emms ask some
> questions (check which player binaries the user has installed, which
> metadata programs are installed, where the music is located, etc.), and
> have Emms generate and write the appropriate elisp configuration.
> I can think of two approaches. I am wondering which, if any, would be
> considered best practice:

I was in that situation a month ago, I want to add what would make this
easier.

Emms is quite flexible which makes the initial setup a little more
complicated.

For example if I want to setup as an mpd client I would want some
defaults that make sense and that can be changed if needed.

I think would make more sense to have defaults for common use cases such
as these then writing a configuration, simplifying the configuration
rather than making it easier to configure.

For example Circe provides defaults for common IRC server's than can be
adjusted individually.

Emms could provide similar defaults.

Br,

Björn



  parent reply	other threads:[~2022-12-10  0:10 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-09 18:04 best practices for implementing Emms configuration Yoni Rabkin
2022-12-09 18:42 ` Akib Azmain Turja
2022-12-10 13:45   ` Yoni Rabkin
2022-12-10 15:46     ` Stefan Monnier
2022-12-09 19:23 ` Stefan Monnier
2022-12-09 23:46   ` Björn Bidar
2022-12-09 23:49     ` Stefan Monnier
2022-12-10 13:54   ` Yoni Rabkin
2022-12-10 14:35     ` Visuwesh
2022-12-10 14:36       ` Visuwesh
2022-12-10 17:56     ` [External] : " Drew Adams
2022-12-10 19:15     ` tomas
2022-12-10  0:10 ` Björn Bidar [this message]
2022-12-10 14:03   ` Yoni Rabkin
2022-12-11  8:02     ` Björn Bidar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sfhoyv8m.fsf@thaodan.de \
    --to=bjorn.bidar@thaodan.de \
    --cc=emacs-devel@gnu.org \
    --cc=yoni@rabkins.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).