zsh-users
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <psprint@zdharma.org>
To: Bart Schaefer <schaefer@brasslantern.com>, Zsh Users <zsh-users@zsh.org>
Subject: Re: A guide to code Zsh natively, without external tools
Date: Wed, 20 Dec 2017 11:01:25 +0100	[thread overview]
Message-ID: <etPan.5a3a34f6.2c2f8963.19e@zdharma.org> (raw)
In-Reply-To: <CAH+w=7ZZUWMN7j-FDegau0Z8p4HGUyQT0ZiZ5RFoW2=WTWVRJg@mail.gmail.com>

On 6 Dec 2017 at 20:58:46, Bart Schaefer (schaefer@brasslantern.com) wrote:
> Thanks, Sebastian. If we ever find a volunteer to update the HTML zsh
> guide, this could be a useful added chapter.

I would want to do this now – after I looked at plugin with 190 commits, of author that seems skilled, and found many forks there. Looks like it's very hard for people to see through unix magic (piping, capturing output, etc). Can I receive a few tips how to contribute the HTML?

But one more thing decided. Microsoft opened PowerShell 1.5 year ago. It now runs on Linux and OS X. My thinking is management of reality, not going into paranoid state and the point is that there's some probability that PowerShell with its piping of objects etc. will make other shells end up like it happened with e.g. Nokia or Blackberry. Bad quality of Zsh scripts created by users might take part in this.

For this reason I would also want to submit zredis module again, as it might yield some strong use case. Innovation is important in not ending up like the two companies.

I also think plugin managers, neglected by Zsh experts, should be rehabilitated now. I'm pretty sure nobody on PowerShell will avoid package managers and stick to startup script. But of course the plugin managers fork etc. and the native-handbook may help.

--  
Sebastian Gniazdowski
psprint /at/ zdharma.org


  reply	other threads:[~2017-12-20 10:14 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
2017-12-20 10:01   ` Sebastian Gniazdowski [this message]
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=etPan.5a3a34f6.2c2f8963.19e@zdharma.org \
    --to=psprint@zdharma.org \
    --cc=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).