From: Marlon Richert <marlon.richert@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: sysexits.h codes? (was: Re: [RFC][PATCH] `newuser` prompt theme)
Date: Tue, 4 May 2021 14:13:59 +0300 [thread overview]
Message-ID: <CAHLkEDvcF4G2rmJxwWbzCNV7OqBZXNjK4WEWEA8qQ_hkq-o3ag@mail.gmail.com> (raw)
In-Reply-To: <20210503160445.GD16336@tarpaulin.shahaf.local2>
On Mon, May 3, 2021 at 7:04 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Marlon Richert wrote on Mon, May 03, 2021 at 14:36:01 +0300:
> >
> > zsh: NO_CLOBBER: file exists; use >| to override
> >
> > It would give you the right keywords to use in a web search.
>
> +1 on putting the option name first.
>
> Not sure whether putting the strerror(3) string in the middle would
> work well in all cases. Convention — codified in errx(3) and friends,
> and compare Perl's «die "foo"» without a trailing newline — is that
> extra information is appended, rather than surrounded. The latter could
> also lead to ambiguous or unclear grammatical structures.
>
> Furthermore, the extra advice in the error wouldn't always be
> appropriate — for instance, when the error is EACCES ("Permission
> denied").
Well, of course not. The advice above is specific to NO_CLOBBER. ;)
In all seriousness, though: I'm fine with not providing advice for
errors like EACCES, because those are not specific to the shell. For
all errors specific to shell features, though, (such as NO_CLOBBER,)
having a short, error-specific piece of advice would be a tremendous
help in making the shell's features easier to discover and easier to
understand.
> Well, suit yourself,
Tweet or plaid? ;)
> but unless someone else shows up to drive the discussion, it'll likely be left at that.
All right, if you insist… :)
I've given it some more thought and the best option, I think, would be
as follows:
* Have an associative array $sysexits.
* Let the keys be the return codes and the values be the exact
descriptions that PRINT_EXIT_VALUE shows (minus the 'zsh: ' prefix and
command suffix, of course).
* Include all of 0 (success), 1 (failure), 2 (error), 64 - 78
(sysexits.h), 126 (command not executable), 127 (command not found),
and 129 - 159 (signal.h). (Anything else I'm forgetting?)
* $sysexits could either be built in, like $signals, or be available
through a module.
Additional features for consideration:
* Make $sysexits editable, so that you can modify what PRINT_EXIT_VALUE outputs.
* Let PRINT_EXIT_VALUE support formatting in the form of prompt escape
sequences.
next prev parent reply other threads:[~2021-05-04 11:15 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-13 19:41 [RFC][PATCH] `newuser` prompt theme Marlon
2021-04-13 20:31 ` Roman Perepelitsa
2021-04-13 20:44 ` Bart Schaefer
2021-04-14 5:09 ` Marlon Richert
2021-04-14 5:17 ` Bart Schaefer
2021-04-14 5:45 ` Marlon
2021-04-14 12:05 ` Daniel Shahaf
2021-04-14 13:17 ` Marlon
2021-04-14 14:09 ` Daniel Shahaf
2021-04-15 1:07 ` Bart Schaefer
2021-04-15 3:50 ` Marlon Richert
2021-04-15 20:27 ` Daniel Shahaf
2021-04-15 23:42 ` Daniel Shahaf
2021-04-15 11:11 ` Mikael Magnusson
2021-04-15 16:44 ` vcs_info's global variables (was: Re: [RFC][PATCH] `newuser` prompt theme) Daniel Shahaf
2021-04-16 16:04 ` [RFC][PATCH] `newuser` prompt theme Marlon
2021-04-16 17:13 ` Daniel Shahaf
2021-04-16 19:19 ` Marlon Richert
2021-04-16 19:30 ` Daniel Shahaf
2021-04-19 16:46 ` Marlon Richert
2021-05-02 17:18 ` Lawrence Velázquez
2021-05-03 2:38 ` Bart Schaefer
2021-05-03 4:11 ` Lawrence Velázquez
2021-05-03 11:38 ` [PATCH] Add customizable `vcs` prompt theme (was Re: [RFC][PATCH] `newuser` prompt theme) Marlon Richert
2021-05-09 18:04 ` Lawrence Velázquez
2021-05-31 1:01 ` Lawrence Velázquez
2021-06-09 12:58 ` Marlon Richert
2021-06-09 13:22 ` Roman Perepelitsa
2021-06-09 18:06 ` Marlon Richert
2021-06-10 9:30 ` Roman Perepelitsa
2021-06-10 13:47 ` Marlon Richert
2021-06-10 14:01 ` Marlon Richert
2021-06-10 17:45 ` Roman Perepelitsa
2021-06-20 22:13 ` Marlon Richert
2021-06-23 17:26 ` Roman Perepelitsa
2022-08-08 10:12 ` Marlon Richert
2022-08-08 10:17 ` Roman Perepelitsa
2021-04-14 14:09 ` sysexits.h codes? (was: " Daniel Shahaf
2021-04-30 19:40 ` Marlon Richert
2021-04-30 21:16 ` Daniel Shahaf
2021-04-30 21:34 ` Bart Schaefer
2021-05-01 15:09 ` Daniel Shahaf
2021-04-30 21:40 ` Bart Schaefer
2021-05-01 13:39 ` Marlon Richert
2021-05-01 14:43 ` Daniel Shahaf
2021-05-03 11:36 ` Marlon Richert
2021-05-03 16:04 ` Daniel Shahaf
2021-05-04 11:13 ` Marlon Richert [this message]
2021-05-21 11:38 ` Marlon Richert
2021-04-14 15:30 ` [RFC][PATCH] `newuser` prompt theme Arseny Maslennikov
2021-04-14 18:52 ` Daniel Shahaf
2021-04-14 14:00 ` precmd hooks and $? Bart Schaefer
2021-04-14 15:18 ` docs patches for precmd hooks and $?, and vcs_info Daniel Shahaf
2021-04-15 2:35 ` Bart Schaefer
2021-04-15 16:17 ` Archives render attachments as first-class messages (was: docs patches for precmd hooks and $?, and vcs_info) Daniel Shahaf
2021-04-15 18:54 ` [RFC][PATCH] Reset ZLE hooks when changing prompt themes (was Re: [RFC][PATCH] `newuser` prompt theme) Marlon
2021-04-15 21:34 ` Daniel Shahaf
2021-04-16 22:34 ` Marlon Richert
2021-04-25 16:08 ` Lawrence Velázquez
2021-05-02 17:03 ` Lawrence Velázquez
2021-05-02 17:59 ` Bart Schaefer
2021-05-05 6:10 ` Marlon Richert
2021-05-16 15:27 ` Lawrence Velázquez
2021-05-16 19:31 ` Marlon Richert
2021-05-17 4:19 ` Bart Schaefer
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=CAHLkEDvcF4G2rmJxwWbzCNV7OqBZXNjK4WEWEA8qQ_hkq-o3ag@mail.gmail.com \
--to=marlon.richert@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@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).