From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Are there zsh error message explanation
Date: Thu, 15 Dec 2022 19:53:04 -0800 [thread overview]
Message-ID: <d1e5ca5b-5ac7-7dbc-debb-71bdfa543aad@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7aUyGNEY2GzO7-UCv3gKq_tffDEQ1jk6HzbgQdxS6aW9Q@mail.gmail.com>
On 2022-12-15 19:28, Bart Schaefer wrote:
>
> We've had this discussion before and decided to stay with the error
> messages that all shells with similar features have in common, even if
> they may be terse.
Not that there's any hope of this, but one of my bright ideas was to
have every error message in the universe include an ID code, which could
be looked up in some reference where they would be elaborated on:
#953: improper type for array assignment
... you look up #953 in the Great Book of Errors and see:
#953: zsh has detected that whereas you have declared (yes I know wrong
word but ...) an array of a certain type, you are attempting to assign
something to that array that is incompatible with it's type. For
example, .... (and so on). So whereas the messages might remain terse,
voluminous information would still be easy to access.
My own error messages optionally return their function and line number,
it can be quite handy.
next prev parent reply other threads:[~2022-12-16 3:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 3:17 empty pipes Ray Andrews
2022-12-12 3:40 ` Bart Schaefer
2022-12-12 14:01 ` Ray Andrews
2022-12-13 2:04 ` Bart Schaefer
2022-12-14 13:05 ` Are there zsh error message explanation Xiao Ling XL Chen
2022-12-15 21:18 ` Daniel Shahaf
2022-12-16 3:28 ` Bart Schaefer
2022-12-16 3:53 ` Ray Andrews [this message]
2022-12-16 4:07 ` Bart Schaefer
2022-12-16 14:16 ` Ray Andrews
2022-12-16 12:47 ` Daniel Shahaf
2022-12-16 14:00 ` Ray Andrews
2022-12-16 1:17 ` empty pipes Ellenor Bjornsdottir
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d1e5ca5b-5ac7-7dbc-debb-71bdfa543aad@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).