Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.0
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :cc:content-type;
        bh=wsJX33h/pOi8VRCGDeEDUSwiBu3ovC4h9D6CW0PIV1M=;
        b=fb51KdKl51B3ig/mLWaFX8NLvCioTtW2OC4inG1rN2NgpBi2j95Z8Ib/Df1NyZS4dh
         kItTyQni40NDxVtWErh1uD1fxR963pjwuCl6ZGrv/98WQ6szsEOQHKPECtxvrouxLaRt
         64v57nENv+EIWoDO32dMAYRMr6d7FUuqnFQihyOCyjzoTsuGxzMYlNdF2h/Y3LAofT5v
         0yZTMzi3GB6L+b19i5kWq7rhcDQeV/UcnteNe3r4JKo7OoE66fcRX9jNGyM4kKs8dkpF
         mml4JvsW5iM6YOquPTus003UmEuBBW/dQTqzU17C+0rtUp/czLUkYplNrjxMxmOYLh3B
         C6Jg==
X-Received: by 10.112.13.99 with SMTP id g3mr39831155lbc.86.1452595037874;
 Tue, 12 Jan 2016 02:37:17 -0800 (PST)
MIME-Version: 1.0
In-Reply-To: <CAKc7PVA2iY4rzcaCmt_Tt0huhQA7O5vyiQ3UWLk_OC=CiC=s1g@mail.gmail.com>
References: <20160110003758.GA28696@tarsus.local2> <CAKc7PVCyRsdt3_pUa3a4qvHGyV=KW9rfBuhZ9f+KmqB_fhih9w@mail.gmail.com>
 <20160110201919.GA17401@tarsus.local2> <CAKc7PVA2iY4rzcaCmt_Tt0huhQA7O5vyiQ3UWLk_OC=CiC=s1g@mail.gmail.com>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Tue, 12 Jan 2016 11:36:58 +0100
Message-ID: <CAKc7PVAgH7YOD+Q0wo2iO0-tOGKbHNpuK=OCTs7WG_YJUbGyVg@mail.gmail.com>
Subject: Re: backward-kill-shell-word widget
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8
X-Seq: zsh-workers 37585

On 11 January 2016 at 09:05, Sebastian Gniazdowski
<sgniazdowski@gmail.com> wrote:
> I gave the example of Antigen code:
>
> local script_loc="$(ls "$location" | grep '\.plugin\.zsh$' | head -n1)

Example code for zgen would be:

for script (${location}/*\.plugin\.zsh(N)) -zgen-source "${script}"

Noshortloops breaks zgen, and short loops are AFAIK harmful as they
limit Zsh's detection of syntax errors. However I currently use zgen
and also tried antigen and OMZ to be in touch with the macrocosm of
Zsh users that has developed around Github. I'm aware they do not code
as Zsh Gods from IRC and mailing lists (not that I code in this way
either, it always amazes me how things in share/$ZSH_VERSION/functions
are constructed), however choose to test on myself what they
developed, to stay in touch with the number of users and trends they
establish. E.g., they developed a "plugin system" that adds plugin's
directory to $fpath. The effect on my system:

% echo $fpath
/Users/sgniazdowski/github/zgen
/Users/sgniazdowski/.zgen/psprint/zsh-navigation-tools-master
/Users/sgniazdowski/.zgen/psprint/zsh-cmd-architect-master
/Users/sgniazdowski/.zgen/psprint/zsh-editing-workbench-master
/usr/local/share/zsh/site-functions /usr/share/zsh/site-functions
/usr/share/zsh/5.0.8/functions

So it's quite flooded (also note that they're prepending). In effect
of the testing, I wonder if one could develop a plugin system without
flooding $fpath?

PS. At least the author didn't use grep. Maybe the code isn't that
bad, haven't looked at it, currently test the things as black boxes.

Best regards,
Sebastian Gniazdowski

