zsh-users
 help / color / mirror / code / Atom feed
From: Thomas Lauer <thomas.lauer@virgin.net>
To: "Thomas Paulsen" <thomas.paulsen@firemail.de>
Cc: "Ray Andrews" <rayandrews@eastlink.ca>, <zsh-users@zsh.org>
Subject: Re: zsh function breaks after error
Date: Fri, 11 Feb 2022 15:07:37 +0000	[thread overview]
Message-ID: <ncuc0hlsqnfl6p0f0pvoqb1m27h8d2rc1u@tlc.com> (raw)
In-Reply-To: <010ebc32f52ad4bbcf733099ae1370d6@firemail.de>

> From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
> --- Ursprüngliche Nachricht ---
> Von: Ray Andrews <rayandrews@eastlink.ca>
> Datum: 10.02.2022 22:26:02
> An: zsh-users@zsh.org
> Betreff: Re: zsh function breaks after error
> 
> 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).
> 
> >mostly the 'complete completer completion completing' stuff -- and I get the 
> feeling no one really understands it fully anyway. 
> I understand and think, we should work out a commented .zshrc step by step project, archiving it, so any newbie has a chance to work out a working .zshrc by himself.

This would certainly help but many things zsh are interconnected in a
way that means that you have to understand something in order to
understand something else... but to understand the first thing you have
to understand the second (I am exaggerating but in a way reading and
trying to digest the zsh docs did remind me of the time when I went
through the Big Blue Book of KIM (this was a 6502-based "microcomputer"
as these things were called then) and tried to understand the 6502 and
its assembler language. I read this book three times before I had the
first tiny glimmer of understanding what it was all about and it took me
another two times to get to grips with the 6502.)

Anyway, if such a project comes into being I would be willing to help
within my capabilities and time constraints. I have written loads of
tech docs over the years so perhaps I could add some value.

Tom


  parent reply	other threads:[~2022-02-11 15:08 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 [this message]
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:
  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=ncuc0hlsqnfl6p0f0pvoqb1m27h8d2rc1u@tlc.com \
    --to=thomas.lauer@virgin.net \
    --cc=rayandrews@eastlink.ca \
    --cc=thomas.paulsen@firemail.de \
    --cc=zsh-users@zsh.org \
    --subject='Re: zsh function breaks after error' \
    /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

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