From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>,
Mauro Aranda <maurooaranda@gmail.com>
Cc: 25152@debbugs.gnu.org
Subject: bug#25152: 25.1; Customize: errors for `restricted-sexp' in `repeat'
Date: Sat, 24 Oct 2020 13:23:51 -0700 (PDT) [thread overview]
Message-ID: <0dc78088-77cb-4dd4-bf41-e22a6621ba33@default> (raw)
In-Reply-To: <878sbve7ja.fsf@gnus.org>
> > I made it just a warning, because this mistake doesn't always result in
> > a messed up buffer. But it can be changed to an error, of course.
>
> A warning sounds good to me, so I've applied your patch to Emacs 28.
FWIW, I disagree that the warning applied is a proper fix.
This is about a message that we show users when they act
in a certain way. The message doesn't correspond to
their action, and it doesn't tell them what we'd like
them to do. It doesn't really tell them anything that's
useful to _them_ (end users), let alone anything that's
actionable.
If I was confused by the behavior enough to report this,
I'm afraid users will also be confused now, with this
attempt to improve the help.
The problem is understood on our end now. That's good.
We're close to a solution that helps users with this.
It's too bad to not give them that help.
The info in the new message is great - info to report
to maintainers. What's missing is the message for
_users_, which is to report that info to a maintainer.
prev parent reply other threads:[~2020-10-24 20:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 18:10 bug#25152: 25.1; Customize: errors for `restricted-sexp' in `repeat' Drew Adams
2016-12-10 4:24 ` npostavs
2016-12-10 4:39 ` Drew Adams
2020-09-05 11:57 ` Mauro Aranda
2020-09-05 14:46 ` Drew Adams
2020-09-05 16:53 ` Mauro Aranda
2020-10-23 12:59 ` Mauro Aranda
2020-10-23 16:47 ` Drew Adams
2020-10-24 12:33 ` Mauro Aranda
2020-10-24 20:16 ` Drew Adams
2020-10-24 19:41 ` Lars Ingebrigtsen
2020-10-24 20:23 ` Drew Adams [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=0dc78088-77cb-4dd4-bf41-e22a6621ba33@default \
--to=drew.adams@oracle.com \
--cc=25152@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=maurooaranda@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).