From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "6572@debbugs.gnu.org" <6572@debbugs.gnu.org>
Subject: bug#6572: 24.0.50; error string from `custom-variable-set'
Date: Mon, 9 May 2022 15:23:07 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488EF03B9ACA19DDA203622F3C69@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87o8064uxx.fsf@gnus.org>
> > This message could & should be more specific,
> > referencing the sexp that defines the restriction
> > the value should respect. E.g., if :type is:
> >
> > (restricted-sexp
> > :match-alternatives
> > (lambda (x) (and (foop x) (not (barp x)))))
> >
> > Then this message is more helpful:
> >
> > "Specified value does not satisfy
> > `(lambda (x) (and (foop x) (not (barp x))))'"
And it's not difficult to provide that help.
> Well, I can see the charm of doing something like this,
> but the Customize interface is for users,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Yes, it is. And that's who we should help, by
fixing this as suggested: users. In this case,
users who try to provide a value that's required,
as specified by that restricted-sexp.
> and telling them
>
> "Specified value does not satisfy
> `(lambda (x) (and (foop x) (not (barp x))))'"
>
> is way too nerdy even for Emacs. Users should look
> at the doc string that will explain this to them in words.
>
> So I'm closing this bug report.
It's not about "charm". It's about helping users.
Users of Customize include everyone, including
users who can understand Lisp. If a user doesn't
understand that improved message, s?he's more
likely to get help from others by providing that
helpful message.
A doc string is important. That doesn't mean we
can't also have better error messages.
Yet another too-bad "I just love closing bugs".
next prev parent reply other threads:[~2022-05-09 15:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-06 15:59 bug#6572: 24.0.50; error string from `custom-variable-set' Drew Adams
2022-05-09 14:55 ` Lars Ingebrigtsen
2022-05-09 15:23 ` Drew Adams [this message]
2022-05-09 15:57 ` Eli Zaretskii
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=SJ0PR10MB5488EF03B9ACA19DDA203622F3C69@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=6572@debbugs.gnu.org \
--cc=larsi@gnus.org \
/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).