From: Bart Schaefer <email@example.com>
To: Ray Andrews <firstname.lastname@example.org>
Cc: Zsh Users <email@example.com>
Subject: Re: zsh function breaks after error
Date: Fri, 11 Feb 2022 15:31:08 -0800 [thread overview]
Message-ID: <CAH+w=7ZT-naqkUTNGN59oNCiG84_OoZG2UQxg+xNPOgGA6Tfirstname.lastname@example.org> (raw)
On Fri, Feb 11, 2022 at 8:00 AM Ray Andrews <email@example.com> wrote:
> Yeah, resources are out there if you just beat the bushes long enough.
> But how about if it were all collated and condensed and
> brought in-house?
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.
The other question that constantly arises is whether the goal is to
make the shell more helpful out of the box for relatively
knowledgeable users, or to make it more attractive to newbies. If the
latter, is the most important thing to give it a flashy appearance?
In either case, where do you draw the line to "get you to 90%"?
next prev parent reply other threads:[~2022-02-11 23:32 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 [this message]
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
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 \
* 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).