zsh-users
 help / color / mirror / code / Atom feed
From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Ray Andrews" <rayandrews@eastlink.ca>
Cc: <zsh-users@zsh.org>
Subject: Re: Re: zsh function breaks after error
Date: Thu, 10 Feb 2022 22:45:04 +0100	[thread overview]
Message-ID: <010ebc32f52ad4bbcf733099ae1370d6@firemail.de> (raw)
In-Reply-To: <44fac8cb-589a-37cf-49b5-47d8836a3647@eastlink.ca>


--- 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.






  reply	other threads:[~2022-02-10 21:45 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 [this message]
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:
  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=010ebc32f52ad4bbcf733099ae1370d6@firemail.de \
    --to=thomas.paulsen@firemail.de \
    --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).