zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Are there zsh error message explanation
Date: Fri, 16 Dec 2022 06:00:44 -0800	[thread overview]
Message-ID: <78fd9f37-149c-ae56-92aa-5af002ff0ef4@eastlink.ca> (raw)
In-Reply-To: <20221216124759.GD8411@tarpaulin.shahaf.local2>


On 2022-12-16 04:47, Daniel Shahaf wrote:
>
> - The error message is unclear and should be improved.  Compatibility
>    doesn't mean we can't ever change the error message; it just limits
>    what changes we will consider.
>
Well said.  I can't remember it exactly but I recall complaining about 
one message that was not only terse it was positively misleading. I 
vaguely recall it being something to the effect that zsh couldn't find 
something, whereas in fact she could find it alright but just didn't 
like it.  Nope, compatibility with inferior traditions is not a virtue.  
The other shells are either extinct or moribund.  Zsh owns the field and 
she should start making the rules, not following them.  Who cares if 
something is compatible with rc shell anymore?  They say that csh was a 
monstrosity from the getgo and is best forgotten, not conformed with.  
Let's have better messages -- or ID's so that you can look up the long 
version.




  reply	other threads:[~2022-12-16 14:01 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
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 [this message]
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=78fd9f37-149c-ae56-92aa-5af002ff0ef4@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).