From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: transpose-words-match (Re: New widget "transpose-segments")
Date: Sat, 9 Jan 2016 19:03:41 +0100 [thread overview]
Message-ID: <CAKc7PVDdF0QHbpseYrZ6FqdAzfLe_iqspQkp1v8nJq3rXqFC2g@mail.gmail.com> (raw)
In-Reply-To: <160109094833.ZM3453@torch.brasslantern.com>
On 9 January 2016 at 18:48, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Jan 9, 9:22am, I asked:
> }
> } How does this differ from
> }
> } zle -N transpose-words transpose-words-match
>
> One difference is that transpose-words-match uses a little more context,
> so
>
> % echo two words<alt-t>
>
> does not transpose because the cursor is not between two words, and
>
> % echo "two <alt-t>words"
> % echo words" "very
>
> swaps around the space even though it is in the middle of a "shell word".
That's a nice catch, finally a de facto difference between
transpose-words-match and transpose-segments. I tried lines like:
$(( i+1 )) a="${(u)a}" 試句相當長
and they worked the same. Now it can be seen that what you described
can also occur inside $(( )).
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-09 18:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-09 11:03 New widget "transpose-segments" 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 [this message]
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
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=CAKc7PVDdF0QHbpseYrZ6FqdAzfLe_iqspQkp1v8nJq3rXqFC2g@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).