From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Yoni Rabkin <yoni@rabkins.net>
Cc: Akib Azmain Turja <akib@disroot.org>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: best practices for implementing Emms configuration
Date: Sat, 10 Dec 2022 10:46:29 -0500 [thread overview]
Message-ID: <jwvmt7vp95e.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <874ju3pe2f.fsf@rabkins.net> (Yoni Rabkin's message of "Sat, 10 Dec 2022 08:45:44 -0500")
>> This is better IMO. Just use Custom. The user can set 'custom-file'
>> to redirect the extra line to somewhere else.
> To be clear though: the goal isn't to present the user with one of the
> customize-group interfaces; I don't use them and wouldn't force anyone
> else to.
To be clear, when I say "use Custom" I mean, let Custom do the saving
for you. That doesn't imply using the Custom UI.
It just means that all the customization needs to be done by setting
vars defined with `defcustom` (and calling something like
`customize-mark-to-save` to tell Custom whats going on) and then saving
the end result with something like `custom-save-all`.
> The idea is to tell the user to invoke "M-x emms-setup", have the user
> answer a few y-or-n-p questions, and write the configuration based on
> that.
Yes, I understand you want to have your own UI for that (sounds like
something occasionally called "a wizard"; you might want to look for
other "wizards" in ELisp).
Stefan
next prev parent reply other threads:[~2022-12-10 15:46 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 [this message]
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=jwvmt7vp95e.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=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.