From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: luangruo@yahoo.com, 57113@debbugs.gnu.org
Subject: bug#57113: 29.0.50; Confusing icon customization interface
Date: Fri, 12 Aug 2022 20:49:58 +0300 [thread overview]
Message-ID: <831qtlnygp.fsf@gnu.org> (raw)
In-Reply-To: <8735e1o4tg.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 12 Aug 2022 17:32:43 +0200)
> Cc: 57113@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 12 Aug 2022 17:32:43 +0200
>
> Po Lu <luangruo@yahoo.com> writes:
>
> > The labels on the various fields should also be more informative than
> > "Repeat", "String" and "Plist"; those only tell you what the fields are,
> > and not what the fields do.
>
> If your point is that Customize sucks for complex structures, you're
> totally correct.
I think we shouldn't offer complex structures as values of user
options to begin with. It makes no sense to me to require users to
understand such structures to be able to customize the respective
features. I think the user options we have whose values are such
complex structures are simply cases of lazy thinking: it is much
easier for a Lisp programmer to make a defcustom that accepts such
complex values than to try to factor them into several simpler ones.
We should flatly reject such user options when they are introduced.
next prev parent reply other threads:[~2022-08-12 17:49 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87h72kxq18.fsf.ref@yahoo.com>
2022-08-10 12:05 ` bug#57113: 29.0.50; Confusing icon customization interface Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 15:32 ` Lars Ingebrigtsen
2022-08-12 17:49 ` Eli Zaretskii [this message]
2022-08-13 1:57 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:01 ` Lars Ingebrigtsen
2022-08-13 12:14 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:23 ` Lars Ingebrigtsen
2022-08-13 12:30 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:35 ` Lars Ingebrigtsen
2022-08-13 12:48 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 5:45 ` Lars Ingebrigtsen
2022-08-15 6:51 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15 6:53 ` Lars Ingebrigtsen
2022-08-15 7:31 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 11:12 ` Mauro Aranda
2023-11-06 13:00 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=831qtlnygp.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=57113@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=luangruo@yahoo.com \
/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).