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: Fri, 11 Feb 2022 19:39:32 -0800	[thread overview]
Message-ID: <82de0721-1560-5686-7c11-990bf2a68de7@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZT-naqkUTNGN59oNCiG84_OoZG2UQxg+xNPOgGA6T-vg@mail.gmail.com>

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 
> 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.
That's why you have several offerings, from basic to ... well, the 
configs could almost become rococo fun-fests, just showing off for the fun
of it.  Don't hafta get anything perfect, just close.

I still vividly remember the very first time I got Linux installed and 
There I am at a stone age prompt and I had some instructions printed off 
(from Windows)
as to what to do next.  Well, it was bash of course, but NO history, NO
backspace key, NO prompt (to speak of) ... other missing stuff, can't 
remember ... anyway it was so
bloody primitive that DOS looked elegant by comparison.  Eventually I got
an editor working and I think it was 'joe' or something, that made edlin 
sophisticated.  I almost quit.  Initiation hazing or something? But, after
jumping to zsh, I remember when I started thinking about prompts -- I 
can't remember where
but there were samples named 'Oliver's prompt' and 'Bart's prompt' and so on
and you picked one and tried it.  Marvelous.  Tune to perfection later, 
in the
mean time it's very good at least.  Suffering is not good for the soul.

  reply	other threads:[~2022-02-12  3:40 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 [this message]
2022-02-22  3:58                         ` Matthew Martin
2022-02-12 16:45                       ` Thomas Lauer
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=82de0721-1560-5686-7c11-990bf2a68de7@eastlink.ca \
    --to=rayandrews@eastlink.ca \
    --cc=zsh-users@zsh.org \
    --subject='Re: zsh function breaks after error' \


* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this 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).