From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 29838@debbugs.gnu.org
Subject: bug#29838: 26.0; Elisp manual: describe standard-error sexps
Date: Sun, 24 Dec 2017 12:05:33 -0800 (PST) [thread overview]
Message-ID: <97c4c503-91cd-4635-8fde-487f22275f02@default> (raw)
In-Reply-To: <831sjkj6iu.fsf@gnu.org>
> >
> > Please explain whatever _can_ be explained.
>
> Sorry, I don't know how to do that in any useful way. Maybe someone
> else will have an idea.
As I said:
A start could to be to mention that an `args-out-of range'
error sexp has the form `(args-out-of-range ARG...)' or
whatever the truth is, and then say what ARG represents,
in general terms.
And as I said:
If [users] saw only nice error messages such as "Args out
of range: [1 2 3 4], -1" then there would be no such problem.
That too would take care of this bug.
Put differently, users should not see a message that refers
to something (internal?) that they cannot understand and
that you say you don't know how to explain. But that's
what happens currently with (as one example), errors raised
on `post-command-hook'.
It is presumably possible to see such unhelpful messages
also in other contexts where raising an error is suppressed
in favor of showing a message about the error. Perhaps a
all such inferior messages could be fixed at the same place
(dunno).
next prev parent reply other threads:[~2017-12-24 20:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-24 17:22 bug#29838: 26.0; Elisp manual: describe standard-error sexps Drew Adams
2017-12-24 18:03 ` Eli Zaretskii
2017-12-24 18:50 ` Drew Adams
2017-12-24 19:00 ` Eli Zaretskii
2017-12-24 20:05 ` Drew Adams [this message]
2022-02-07 10:09 ` Lars Ingebrigtsen
2017-12-24 18:54 ` Drew Adams
2017-12-24 19:57 ` Andreas Schwab
2017-12-24 20:10 ` Drew Adams
2017-12-25 8:52 ` Andreas Schwab
2017-12-25 16:28 ` 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=97c4c503-91cd-4635-8fde-487f22275f02@default \
--to=drew.adams@oracle.com \
--cc=29838@debbugs.gnu.org \
--cc=eliz@gnu.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).