help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: zsh function breaks after error
Date: Sat, 12 Feb 2022 09:48:51 -0800	[thread overview]
Message-ID: <9d8f3fec-2402-a40e-394a-8d0270239c37@eastlink.ca> (raw)
In-Reply-To: <0lof0hlr1tmbrfipg2pu27o63od4d3ni0j@tlc.com>

On 2022-02-12 08:45, Thomas Lauer wrote:
> Interesting. Take Command *was* (or is) powerful but IMO it's no match
> for zsh.
Indeed not.  Zsh is 'bigger' and more powerful in every way, but also 
less consistent.
To some degree this is inevitable and quite forgivable.  Projects that 
grow by accretion
must encounter this sort of thing and solutions are far from simple.

I am with Bart on this one. Many so-called "defaults" in all sorts of
> software, including zsh, are far removed from what I find reasonable (or
> at least work-flow enhancing). The whole point of "optionising" features
> is to give people choice. But with that comes of course a learning curve
> and some responsibility for the choices one makes.
Sure, so my notion of several different default configurations gives you 
several possible starting
points, and then invites you and helps you to start customizing. The 
difference is that
instead of starting from 'zero',  you're starting from one of a suite of 
configurations that
are considered reasonable by real users.  And of course the 'zero 
option' would be there
as well so all of the above can be ignored as desired.

      reply	other threads:[~2022-02-12 17:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-08 17:16 Thomas Lauer
2022-02-09 15:18 ` Bart Schaefer
2022-02-09 18:45   ` Thomas Lauer
2022-02-09 20:16     ` Bart Schaefer
2022-02-10 13:55       ` Thomas Lauer
2022-02-10 13:59         ` Roman Perepelitsa
2022-02-10 16:20           ` Thomas Lauer
2022-02-10 16:48             ` Roman Perepelitsa
2022-02-10 17:20               ` Thomas Lauer
2022-02-10 21:26                 ` Ray Andrews
2022-02-10 21:45                   ` Thomas Paulsen
2022-02-10 23:37                     ` Daniel Shahaf
2022-02-11 15:07                     ` Thomas Lauer
2022-02-11 14:58                   ` Thomas Lauer
2022-02-11 15:59                     ` Ray Andrews
2022-02-11 23:31                       ` Bart Schaefer
2022-02-12  3:39                         ` Ray Andrews
2022-02-22  3:58                         ` Matthew Martin
2022-02-12 16:45                       ` Thomas Lauer
2022-02-12 17:48                         ` Ray Andrews [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9d8f3fec-2402-a40e-394a-8d0270239c37@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \


* 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


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).