Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
Date: Sun, 10 Jan 2016 20:13:25 +0000
From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: backward-kill-shell-word widget
Message-ID: <20160110201325.GD1997@tarsus.local2>
References: <20160110003758.GA28696@tarsus.local2>
 <CAKc7PVA9kaqCv2fNhpw5vGv4zR3DB3W2f-pnZfnx5t-xZFs7KA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAKc7PVA9kaqCv2fNhpw5vGv4zR3DB3W2f-pnZfnx5t-xZFs7KA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)

Sebastian Gniazdowski wrote on Sun, Jan 10, 2016 at 08:42:23 +0100:
> On 1 January 2016 at 01:37, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> > If you use zsh 5.1.1 or older, comment the 'zle -f' line.  (Without that
> > line, using this widget followed by another kill followed by a yank
> > won't include the text this widget killed in the yank.)
> 
> So you submit for people, not for commit? You could use is-at-least to
> submit for commit?

Compatibility is not the point; maintenance burden is.

If the functionality my widget provides can be implemented in terms of
existing widgets, then (a) perhaps my widget doesn't need to be
committed at all, and (b) if it _is_ to be committed, it should be
reimplemented in terms of existing widgets, if possible.

Similarly, when I asked whether there is anything my widget does
existing widgets don't, the point was that perhaps those widgets could
be improved.  For example, if my widget worked on Tuesdays and the
existing widgets didn't, then teaching select-in-shell-word or
"select-word-style shell" to work on Tuesdays would improve all widgets
implemented in terms of those two widgets, not only b-k-s-word.

Cheers,

Daniel