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 10:50:16 -0800 (PST) [thread overview]
Message-ID: <cd9aea24-52a1-4b13-a8f0-29892826cf7d@default> (raw)
In-Reply-To: <837etcj95f.fsf@gnu.org>
> > Looking at the manual coverage of sequence etc. functions, you find
> > information such as this:
> > (elt [1 2 3 4] -1)
> > error→ Args out of range: [1 2 3 4], -1
> > But that doesn't help for understanding `(args-out-of-range 9 9)'.
>
> Not sure what you want to explain and how. The number of arguments
> shown by the args-out-of-range error is not fixed (although in many
> cases they are just 2), and their number and meaning are determined by
> the calling application. It's not something fixed that can be
> described to match all the uses.
Please explain whatever _can_ be explained. Clearly, if the
number and specific meanings of arguments cannot be known
generically then that info cannot be conveyed. But so far,
nothing at all is told users about a sexp such as
`(args-out-of-range 9 9)'.
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.
The error messages themselves (see above) are quite
different. They show you the sequence/array/whatever
as well as the args that are out of range for it.
(And a user would naturally expect, I think, that
the info in something like `(args-out-of-range 9 9)'
would provide the range that the args are outside of,
as well as the arg values that are outside that range,
even if it didn't provide the sequence/array/etc.)
next prev parent reply other threads:[~2017-12-24 18:50 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 [this message]
2017-12-24 19:00 ` Eli Zaretskii
2017-12-24 20:05 ` Drew Adams
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=cd9aea24-52a1-4b13-a8f0-29892826cf7d@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).