Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
MIME-Version: 1.0
In-Reply-To: <20160110003758.GA28696@tarsus.local2>
References: <20160110003758.GA28696@tarsus.local2>
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Sun, 10 Jan 2016 16:50:50 +0100
Message-ID: <CAKc7PVCyRsdt3_pUa3a4qvHGyV=KW9rfBuhZ9f+KmqB_fhih9w@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
Content-Transfer-Encoding: quoted-printable

Hello
How about such project?

https://github.com/psprint/zsh-editing-workbench

Pros:
- if transpose-shell-words and/or your backward-kill-shell-word will
be commited, then somewhere near zsh-6.2 an user will be allowed to
expect "it works everywhere, I can always copy my .zshrc and use the
widgets"
- by creating the project the functionality will be provided to all
zsh versions, even zsh 4.x
- all editing functionalities grasped by a group of people,
configured, provided =E2=80=93 sum of parts is more than set of parts, we w=
ill
be able to obtain cool things and provide them in sane manner, with
sane shortcuts etc.

If I'm to work alone on the project, I need at least your permission
to use backward-kill-shell-word under GPLv3 and MIT. Can I please?

I used the github originated plugin architecture. I'm not into this
very much, the code is often naive, for example this is how Antigen
looks for files to source:

        local script_loc=3D"$(ls "$location" | grep '\.plugin\.zsh$' | head=
 -n1)"

The plugin architecture is: add plugin to $fpath, source
".plugin.zsh". Maybe there is a flaw in this and it can be done
better, not sure.

Best regards,
Sebastian Gniazdowski