zsh-workers
 help / color / mirror / code / Atom feed
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: New widget "transpose-segments"
Date: Tue, 12 Jan 2016 10:50:30 +0100	[thread overview]
Message-ID: <CAKc7PVAno-RQBnu+ZZ_C8gbDUr_pHi3vGU-z=E=PyEzpKjbHrQ@mail.gmail.com> (raw)
In-Reply-To: <160112000929.ZM6837@torch.brasslantern.com>

On 12 January 2016 at 09:09, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 9,  6:59pm, Sebastian Gniazdowski wrote:
> }
> } The main difference is working across newlines. Also, the requirement
> } to position cursor at beginning of word to transpose is absent. I
> } think those two are important.
>
> Patches for both of these sent a little while ago.
>
> } Also, setting word style is not needed.
>
> I have no real objection to including either your widget or Daniel's,
> but the number of different ways to do the almost but not quote the
> same thing begins to be overwhelming

In my project Zew I quite track what's going on here and it should
there clarify if transpose-segments and other widgets have real reason
to exist (besides providing functionality for zsh < 5.2-dev-0)

> However, I should note that I would rather that we don't introduce yet
> another term ("segments") to mean "shell words".

Yeah I already renamed "transpose-segments" to "transpose-shell-words" in Zew.

Best regards,
Sebastian Gniazdowski


      reply	other threads:[~2016-01-12  9:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-09 11:03 Sebastian Gniazdowski
2016-01-09 12:19 ` Jérémie Roquet
2016-01-09 15:56   ` Sebastian Gniazdowski
2016-01-09 15:55 ` Sebastian Gniazdowski
2016-01-09 15:57   ` Sebastian Gniazdowski
2016-01-09 17:22 ` Bart Schaefer
2016-01-09 17:48   ` transpose-words-match (Re: New widget "transpose-segments") Bart Schaefer
2016-01-09 18:03     ` Sebastian Gniazdowski
2016-01-09 18:18       ` Bart Schaefer
2016-01-11 13:13         ` Sebastian Gniazdowski
2016-01-12  6:26           ` Bart Schaefer
2016-01-12  6:46             ` Bart Schaefer
2016-01-12  9:09               ` Sebastian Gniazdowski
2016-01-12  9:39                 ` Sebastian Gniazdowski
2016-01-12  9:23             ` Sebastian Gniazdowski
2016-01-12  9:38               ` Sebastian Gniazdowski
2016-01-12  9:46               ` Peter Stephenson
2016-01-12 19:12               ` Bart Schaefer
2016-01-09 17:59   ` New widget "transpose-segments" Sebastian Gniazdowski
2016-01-09 19:06     ` Sebastian Gniazdowski
2016-01-12  8:13       ` Bart Schaefer
2016-01-12  8:09     ` Bart Schaefer
2016-01-12  9:50       ` Sebastian Gniazdowski [this message]

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='CAKc7PVAno-RQBnu+ZZ_C8gbDUr_pHi3vGU-z=E=PyEzpKjbHrQ@mail.gmail.com' \
    --to=sgniazdowski@gmail.com \
    --cc=schaefer@brasslantern.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).