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: Mon, 11 Jan 2016 14:13:31 +0100 [thread overview]
Message-ID: <CAKc7PVC9TBCVtC=ijqJMtcVqcojEi+4Zf4rW_R_gqDgr4NOvAg@mail.gmail.com> (raw)
In-Reply-To: <160109101801.ZM3561@torch.brasslantern.com>
On 9 January 2016 at 19:18, Bart Schaefer <schaefer@brasslantern.com> wrote:
> Yes, I'm just not sure it's an *intentional* difference.
Bart there already is "copy-prev-shell-word". It's good to not be
bound to global select-word-style setting. My widget named
"transpose-shell-words" and your simple "backward-kill-shell-word"
(the one for zsh >= 5.0.8) together with "copy-prev-shell-word" would
constitute a nice feature set. And I'm using Daniel's
"backward-kill-shell-word" in my Zew so that all Zsh users, even
before zsh-5.0.8 can be happy
That said I tested your bksw and it doesn't fully work for following
multi-line command:
a=${(j:,:)a}
a="${(r:100000:: _:)a}"
試句相當長
""
a\ b
c\ b
There is a space after "". When cursor is positioned after this space,
invoking bksw joins lines "" and a\ b instead of deleting "". Daniel's
code works on this. It's not the first time that (z) flags proves its
robustness, but maybe your simpler bksw can be updated to handle this
case?
Best regards,
Sebastian Gniazdowski
next prev parent reply other threads:[~2016-01-11 13:13 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
2016-01-09 18:18 ` Bart Schaefer
2016-01-11 13:13 ` Sebastian Gniazdowski [this message]
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='CAKc7PVC9TBCVtC=ijqJMtcVqcojEi+4Zf4rW_R_gqDgr4NOvAg@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).