From: Jean Louis <bugs@gnu.support>
To: Philip Kaludercic <philipk@posteo.net>
Cc: emacs-devel@gnu.org
Subject: Re: Infrastructure for packages to suggest customizations
Date: Tue, 16 Feb 2021 09:09:27 +0300 [thread overview]
Message-ID: <YCthl6D7o5dkz153@protected.rcdrun.com> (raw)
In-Reply-To: <877dn8bytq.fsf@posteo.net>
* Philip Kaludercic <philipk@posteo.net> [2021-02-16 04:17]:
> There are a few things I am not satisfied with, such as that the default
> behaviour for package-suggest-configuration is to just append the
> generated configuration to `custom-file' or `user-init-file'. Part of my
> intention was to generate code that can easily be changed and adapted by
> the user (unlike custom-set-variables), so I don't analyse the files
> themselves. This might not look nice in some cases, but then again,
> these people are probably not the ones using this feature
It should be in the user's init file. Those suggestions could define custom
variables and use custom interface to save them.
> Another point is that package-suggest-configuration has an option such
> that the command will not change anything (PREVIEW, activated with a
> prefix argument). I was wondering if it would make sense to make this
> the default behaviour whenever the command is invoked interactively.
In my opinion it should change as that helps users. It is always better that
computer assists human in full.
Another point is that those suggestions, if you think they could be intrusive
or become intrusive too much, should be enabled by the will of the user.
If it becomes part of NEWS then I suggest that users first have to enable the
option to be asked about that. But if not too intrusive, maybe it should be by default.
In general, questions like that should be asked once automatically, and user
shall be told how to customize it again or how to get asked again manuall.
prev parent reply other threads:[~2021-02-16 6:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 1:12 Infrastructure for packages to suggest customizations Philip Kaludercic
2021-02-16 2:37 ` Stefan Monnier
2021-02-16 11:18 ` Philip Kaludercic
2021-02-16 6:09 ` Jean Louis [this message]
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=YCthl6D7o5dkz153@protected.rcdrun.com \
--to=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.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).