From: Akib Azmain Turja <akib@disroot.org>
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 00:42:25 +0600 [thread overview]
Message-ID: <87mt7wmnam.fsf@disroot.org> (raw)
In-Reply-To: <87pmcspi77.fsf@rabkins.net> (Yoni Rabkin's message of "Fri, 09 Dec 2022 13:04:12 -0500")
[-- Attachment #1: Type: text/plain, Size: 1912 bytes --]
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:
>
> Write the configuration to the user's ~/.emacs in the same manner as "
> ;; custom-set-variables was added by Custom." or ";; Added by
> Package.el." I'm not a huge fan of this option for the sole reason that
> I don't appreciate packages automatically editing a file I manually
> edit.
This is better IMO. Just use Custom. The user can set 'custom-file'
to redirect the extra line to somewhere else.
>
> XOR
>
> Write the configuration to ~/.emacs.d/emms/auto-config.el. Emms would
> then look for that configuration file there during startup. This is
> cleaner, and can have the benefit of Emms being configured without a
> single line needing to be added by the user to their ~/.emacs.
Not bad, but is there really any need to reinvent the wheel once again?
>
> I know that a bunch of packages store information in ~/.emacs.d/, just
> as Emms does. But is it acceptable practice to store configuration there
> too?
>
> What I'm looking for is something along the lines of: "sure, we don't
> care", or "don't do that, we don't want Emacs packages to go down that
> route", or something similar.
>
> Thank you in advance.
--
Akib Azmain Turja, GPG key: 70018CE5819F17A3BBA666AFE74F0EFA922AE7F5
Fediverse: akib@hostux.social
Codeberg: akib
emailselfdefense.fsf.org | "Nothing can be secure without encryption."
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2022-12-09 18:42 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mt7wmnam.fsf@disroot.org \
--to=akib@disroot.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.