Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: backward-kill-shell-word widget
- X-seq: zsh-workers 37553
- From: Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx>
- To: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- Subject: Re: backward-kill-shell-word widget
- Date: Sun, 10 Jan 2016 20:13:25 +0000
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= daniel.shahaf.name; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=MYKWnhPqrxPWWaX+ zWSRn8V3l1c=; b=KlAOC/eC6mzpm+D7XLwvvS7llAd4NmtsmuamHiEld8Rd3spu H+jiuyG81e2hByvKviQ+kDqrblD9pqufIbUEcjB18kB78JcpA/zGNWSXavxDQTKQ xTaARqZuhoNYXgNHpJxia1mM3A9e48ML0XkfkXUU8oLJAGv9Z9pUibA2dC8=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-sasl-enc:x-sasl-enc; s=smtpout; bh=MYKWnhPqrxPWWaX +zWSRn8V3l1c=; b=FQBJob0gD/rs1oT0/VPYyswqRb9uqRAdi7KoUqSC19F6ltW USwZv0KPBf3Kq/tAcFdmu35NSVr2z6QtaJz47xiVpYTBGmejJ2T0tViW78bgllNj 7D3LZw8vdb/cAzuczW/qKXzcfi/kh2rFWB4jWi8lnetNgAgMFvE9uZCvn+l0=
- In-reply-to: <CAKc7PVA9kaqCv2fNhpw5vGv4zR3DB3W2f-pnZfnx5t-xZFs7KA@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <20160110003758.GA28696@tarsus.local2> <CAKc7PVA9kaqCv2fNhpw5vGv4zR3DB3W2f-pnZfnx5t-xZFs7KA@mail.gmail.com>
Sebastian Gniazdowski wrote on Sun, Jan 10, 2016 at 08:42:23 +0100:
> On 1 January 2016 at 01:37, Daniel Shahaf <d.s@xxxxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author