From: Daniel Shahaf <d.s@daniel.shahaf.name>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: backward-kill-shell-word widget
Date: Sun, 10 Jan 2016 19:53:23 +0000 [thread overview]
Message-ID: <20160110195323.GA23064@tarsus.local2> (raw)
In-Reply-To: <160110091744.ZM585@torch.brasslantern.com>
Bart Schaefer wrote on Sun, Jan 10, 2016 at 09:17:44 -0800:
> On Jan 1, 12:37am, Daniel Shahaf wrote:
> }
> } This widget is like ^W but for "shell words" rather than
> } whitespace-separated words, so
> }
> } % echo foo "bar baz" <CURSOR>^W
> } becomes
> } % echo foo <CURSOR>
>
> As of 5.0.8 you can do this with:
>
> backward-kill-shell-word() {
> zle select-in-shell-word
> ((++CURSOR)) # adjust for vi vs. emacs region
> zle kill-region
I'd add:
LBUFFER+=" "
Without that, LBUFFER[-1] after the widget is the last character of the
preceding word.
> }
>
> I'm not sure if that CURSOR adjustment is a a bug or just a necessary
> evil because of using vi binding in the emacs keymap.
Thanks for the additional solution!
next prev parent reply other threads:[~2016-01-10 19:53 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
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 [this message]
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=20160110195323.GA23064@tarsus.local2 \
--to=d.s@daniel.shahaf.name \
--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).