From: Lars Ingebrigtsen <larsi@gnus.org>
To: dalanicolai@gmail.com
Cc: 39887@debbugs.gnu.org
Subject: bug#39887: 26.3; Customize buffer does not show type expected
Date: Mon, 26 Oct 2020 22:48:29 +0100 [thread overview]
Message-ID: <877drcu09e.fsf@gnus.org> (raw)
In-Reply-To: <2b1287b530e902d23c7c28cdd05dbf482ec97450.camel@gmail.com> (dalanicolai@gmail.com's message of "Tue, 03 Mar 2020 18:06:25 +0100")
dalanicolai@gmail.com writes:
> The title already explains the bug. It would be great if the customize
> buffer shows which type of variable is expected. Although the :type
> keyword is included in the defcustom declaration, it is not shown in
> the customization buffer which type is expected. If the wrong type is
> filled in then the only error message given is "(mismatch)". Quite
> some package writers do not - additionally - document their variables.
The Customize buffer is supposed to be a user-friendly, easy interface
to use, and displaying types like
(alist :key-type symbol :value-type (choice symbol integer))
which only would make sense to a programmer would be the wrong way to go
here. The Customize interface already tries to guide the users as much
as the type spec allows.
I'm sure there are individual doc strings that could stand improving,
though, in which case bug reports for those would be welcome. But I'm
closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-10-26 21:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:06 bug#39887: 26.3; Customize buffer does not show type expected dalanicolai
2020-03-03 19:17 ` Drew Adams
2020-10-26 21:48 ` Lars Ingebrigtsen [this message]
2020-10-26 22:51 ` Drew Adams
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=877drcu09e.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=39887@debbugs.gnu.org \
--cc=dalanicolai@gmail.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).