From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: thoughts on failure messages in UI/UX...
Date: Thu, 17 Dec 2020 23:25:53 +0000 [thread overview]
Message-ID: <20201217232553.GA14131@dcvr> (raw)
Most command-line programs in AOT compiled languages won't
emit line numbers on failures.
On the flip side, languages like Python/Ruby spew huge
stack traces on failures that most users probably glaze over
(I know I do :P)
Perl die("no trailing newline") will emit the line number it's
called from, but die("newline exists\n") omits the line number.
I'm thinking we should favor showing the line number since
anybody running our code already has the source available
(this is why I prefer scripting languages).
That would allow users to open that code in $EDITOR and poke
around. If they need to, they can replace the die() call with
Carp::confess/longmess to dump stack.
reply other threads:[~2020-12-17 23:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201217232553.GA14131@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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.
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).