zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: backward-kill-shell-word widget
Date: Sun, 10 Jan 2016 16:50:50 +0100	[thread overview]
Message-ID: <CAKc7PVCyRsdt3_pUa3a4qvHGyV=KW9rfBuhZ9f+KmqB_fhih9w@mail.gmail.com> (raw)
In-Reply-To: <20160110003758.GA28696@tarsus.local2>

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 – sum of parts is more than set of parts, we will
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="$(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


  parent reply	other threads:[~2016-01-10 15:51 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
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 [this message]
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='CAKc7PVCyRsdt3_pUa3a4qvHGyV=KW9rfBuhZ9f+KmqB_fhih9w@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --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).