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: Fri, 11 Feb 2022 14:58:01 +0000 [thread overview]
Message-ID: <chtc0htcb245f0s1hvm0lrst8rc63rhcfq@tlc.com> (raw)
In-Reply-To: <44fac8cb-589a-37cf-49b5-47d8836a3647@eastlink.ca>
> From: Ray Andrews <rayandrews@eastlink.ca>
> On 2022-02-10 09:20, Thomas Lauer wrote:
> >
> > (there are so many
> > options there that I have no idea when or even why I did include this).
> >
> When I first got involved I learned to turn absolutely everything
> 'config' off except for my one and only .zshrc file so that I'd at least
> know where to look if things went strange. Then I picked a sample
> .zshrc on faith off the internet and slowly by trial and error figured
> out what half of it does. The other half is still a mystery, mostly the
> 'complete completer completion completing' stuff -- and I get the
> feeling no one really understands it fully anyway. Like with everything
> else, the docs assume you are already an expert. But a beginner's guide
> to configuration would have sure been nice. I bitched about this a
> little bit: the setup utility should offer you several config options
> complete with a brief description of what each one offers. Mind, I was
> coming from DOS whereas most zsh converts are already shell experts, so
> my culture shock was much worse than for most.
Well... I tend to know what I am doing and I think (or thought) that all
the options in my .zshrc are there for a reason. I literally went
through the options documentation one by one over a few days, looked
into each option and (tried to understand and) decide whether it was a
Good (tm) thing or not. For most options this worked pretty well, but
there were a few which were then over my head (probably some still are).
But I agree that the density of the documentation can be a problem,
especially for people who are no developers and are perhaps not used to
dense docs :-)
I'm a Windows refugee as well but over there I've used a command
processor called Take Command (the former 4NT) for decades and so I was
already used to a powerful and complex beast of a shell.
And yes, the completion still is mostly a mystery but with judicious use
of Google, Stackexchange, Reddit etc etc and a lot of trial and error I
have cobbled together something that works pretty much as I want.
Actually it was the completion that convinced me to drop bash and start
using zsh.
But if there ever was a case of YMMV *and* RTFM then zsh must be it:-)
Tom
next prev parent reply other threads:[~2022-02-11 14:59 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 [this message]
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
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=chtc0htcb245f0s1hvm0lrst8rc63rhcfq@tlc.com \
--to=thomas.lauer@virgin.net \
--cc=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).