zsh-workers
 help / color / mirror / code / Atom feed
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
Date: Sun, 10 Jan 2016 20:13:25 +0000	[thread overview]
Message-ID: <20160110201325.GD1997@tarsus.local2> (raw)
In-Reply-To: <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@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


  parent reply	other threads:[~2016-01-10 20:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-01  0:37 Daniel Shahaf
2016-01-10  7:42 ` Sebastian Gniazdowski
2016-01-10  7:54   ` Sebastian Gniazdowski
2016-01-10 20:13   ` Daniel Shahaf [this message]
2016-01-10 13:37 ` Sebastian Gniazdowski
2016-01-10 19:59   ` Daniel Shahaf
2016-01-10 21:06     ` Bart Schaefer
2016-01-12  8:23   ` Bart Schaefer
2016-01-10 15:50 ` Sebastian Gniazdowski
2016-01-10 20:19   ` Daniel Shahaf
2016-01-11  8:05     ` Sebastian Gniazdowski
2016-01-12 10:36       ` Sebastian Gniazdowski
2016-01-13  1:18       ` Daniel Shahaf
2016-01-13  8:38         ` Sebastian Gniazdowski
2016-01-14  0:13           ` Daniel Shahaf
2016-01-14  6:54             ` Bart Schaefer
2016-01-15  6:26               ` Daniel Shahaf
2016-01-10 17:17 ` Bart Schaefer
2016-01-10 19:53   ` Daniel Shahaf
2016-01-12  7:54     ` Bart Schaefer
2016-04-14 16:21   ` Bart Schaefer
2016-07-08 14:19   ` Oliver Kiddle
2016-01-11 11:53 ` Sebastian Gniazdowski
2016-01-12  6:59   ` Bart Schaefer
2016-01-12  7:49     ` Sebastian Gniazdowski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160110201325.GD1997@tarsus.local2 \
    --to=d.s@daniel.shahaf.name \
    --cc=sgniazdowski@gmail.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).