From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: A guide to code Zsh natively, without external tools
Date: Wed, 6 Dec 2017 11:58:46 -0800 [thread overview]
Message-ID: <CAH+w=7ZZUWMN7j-FDegau0Z8p4HGUyQT0ZiZ5RFoW2=WTWVRJg@mail.gmail.com> (raw)
In-Reply-To: <etPan.5a2816f9.268df5e9.c73c@zdharma.org>
On Wed, Dec 6, 2017 at 8:12 AM, Sebastian Gniazdowski
<psprint@zdharma.org> wrote:
> When writing Zsh plugins I learned (i.a. thanks to #zsh channel) how to avoid forks to external tools, for speed and lack of dependencies. I've put this experience into Asciidoc
Thanks, Sebastian. If we ever find a volunteer to update the HTML zsh
guide, this could be a useful added chapter.
next prev parent reply other threads:[~2017-12-06 19:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-06 16:12 Sebastian Gniazdowski
2017-12-06 19:58 ` Bart Schaefer [this message]
2017-12-20 10:01 ` Sebastian Gniazdowski
2017-12-20 11:53 ` Eric Cook
2017-12-20 12:01 ` Eric Cook
2017-12-20 14:18 ` Sebastian Gniazdowski
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='CAH+w=7ZZUWMN7j-FDegau0Z8p4HGUyQT0ZiZ5RFoW2=WTWVRJg@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--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).