all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yoni Rabkin <yoni@rabkins.net>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: best practices for implementing Emms configuration
Date: Sat, 10 Dec 2022 08:54:02 -0500	[thread overview]
Message-ID: <87zgbvnz45.fsf@rabkins.net> (raw)
In-Reply-To: <jwvr0x8qtcn.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Fri, 09 Dec 2022 14:23:12 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

>> 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.
>
> AFAIK people who don't like/want Emacs to edit their manually-edited
> config file (such as myself) should and do set `custom-file` accordingly.

Over the years, the people I've helped set up Emms have almost always
been people who don't know elisp at all (makes sense when you think
about it). I think that the people who know about, and use `custom-file'
are also the people who don't need help setting up Emms.

However, that doesn't mean that you are wrong.

> So the better option seems very definitely to just save the config via
> Custom: that's what it's for.

I'll look at cus-edit.el to see how I can leverage Custom to do the
saving and loading for me outside of the customize interface. I don't
use it and am ignorant of it.

>> 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.
>
> I personally dislike it when packages do such things because it's never
> completely clear how it interacts with the settings I put into my own
> manually-edited init file.
>
> Custom suffers from the same problems, of course, but once you've
> learned how it works, then this carries over to all the packages
> that use it.
>
>> 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?
>
> There's no law against it.  But as a user, I'd vote against it.

That vote is important. Thank you for taking the time and effort to cast
it.

-- 
   "Cut your own wood and it will warm you twice"



  parent reply	other threads:[~2022-12-10 13:54 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 [this message]
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=87zgbvnz45.fsf@rabkins.net \
    --to=yoni@rabkins.net \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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.