help / color / mirror / code / Atom feed
From: Thomas Lauer <thomas.lauer@virgin.net>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: zsh function breaks after error
Date: Sat, 12 Feb 2022 16:45:00 +0000	[thread overview]
Message-ID: <0lof0hlr1tmbrfipg2pu27o63od4d3ni0j@tlc.com> (raw)
In-Reply-To: <aa008389-b294-ff33-05e6-7e174a157f4b@eastlink.ca>

> From: Ray Andrews <rayandrews@eastlink.ca>
> On 2022-02-11 06:58, Thomas Lauer wrote:
> > I'm a Windows refugee as well but over there I've used a command
> > processor called Take Command (the former 4NT)
> 4DOS and Take Command ruined me.  I got to just taking for granted that 
> level of
> polished perfection and when I moved over here,  the culture shock
> nearly killed me.

Interesting. Take Command *was* (or is) powerful but IMO it's no match
for zsh. I happily invested a lot of time investigating zsh and its
options because I found many things immediately appealing.

> On 2022-02-11 15:31, Bart Schaefer wrote:
> >
> > Consensus is hard.  For example, I personally I think tens of
> > thousands of lines of history is unnecessary no matter how much RAM
> > you have to throw at  it.
> I picked that line almost at random.  Thinking about it, mine probably 
> is too big.
> Point is that some reasonable amount of history is something that almost 
> everyone
> wants.

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.


  parent reply	other threads:[~2022-02-12 16:45 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 [this message]
2022-02-12 17:48                         ` Ray Andrews

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=0lof0hlr1tmbrfipg2pu27o63od4d3ni0j@tlc.com \
    --to=thomas.lauer@virgin.net \
    --cc=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).