From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11296 invoked by alias); 29 Nov 2017 09:22:17 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: List-Unsubscribe: X-Seq: 22993 Received: (qmail 18066 invoked by uid 1010); 29 Nov 2017 09:22:17 -0000 X-Qmail-Scanner-Diagnostics: from aok120.rev.netart.pl by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(85.128.245.120):SA:0(-1.9/5.0):. Processed in 5.888463 secs); 29 Nov 2017 09:22:17 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: psprint@zdharma.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | X-Virus-Scanned: by amavisd-new using ClamAV (8) Date: Wed, 29 Nov 2017 10:22:08 +0100 From: Sebastian Gniazdowski To: Zsh Users Message-ID: Subject: Promoting writing Zshell software not scripts =?utf-8?Q?=E2=80=93=C2=A0Help_?=Wanted X-Mailer: Airmail (442) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hello, plugins for Zshell have serious flaw: =22works -> next=22 approach, typic= al for writing scripts or zshrc. The effect is low commit count (3-30) an= d a state of =22you can fiddle with it=22. The idea: Github asciidoc document listing 100-or-more commit projects: https://github.com/zdharma/Zsh-100-Commits-Club Motivation: =C2=A0- there are so many 3-30 commit plugins that its actually hard to u= se plugins in general, the flood literaly blocks good projects, =C2=A0=E2=80=93 creating mindset alternative to Advanced Bash Scripting G= uide mindset, which is about writing top-down scripts, using grep, sed, e= tc., reading data via var=3D( =60ls -1=60 ), etc., being clever in doing = this (it is indeed a challenge to code like that); such mindset is the pr= omotion of writing software not scripts. My first question: what quality traits can be easily checked in Zsh scrip= t code=3F I currently have a) has tests, b) generated docs, c) is using a= utoload, d) is using warn=5Fcreate=5Fglobal, e) is using Travis CI to do = continuous building with tests. My second question: would anyone contribute to=C2=A0https://github.com/zd= harma/Zsh-100-Commits-Club =3F It is hard to analyze and test multiple pl= ugins, I might have started a half-year project if I will do this alone. PS. I have 2.5 year experience in delivering 100, 200 or recently 1000 co= mmits per Zshell project and have good insight what is a difference betwe= en a software and a script. But I think everyone can also get correct con= clusions per-logic if needed, so I skipped this part. -- =20 Sebastian Gniazdowski psprint /at/ zdharma.org