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: Thu, 10 Feb 2022 13:26:02 -0800	[thread overview]
Message-ID: <44fac8cb-589a-37cf-49b5-47d8836a3647@eastlink.ca> (raw)
In-Reply-To: <t4ia0hhhtfrq5vg133rts7a4uf9c8qvl8t@tlc.com>

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.

  reply	other threads:[~2022-02-10 21:26 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 [this message]
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

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=44fac8cb-589a-37cf-49b5-47d8836a3647@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).