Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <160111235409.ZM6788@torch.brasslantern.com>
Date: Mon, 11 Jan 2016 23:54:09 -0800
In-Reply-To: <20160110195323.GA23064@tarsus.local2>
Comments: In reply to Daniel Shahaf <d.s@daniel.shahaf.name>
        "Re: backward-kill-shell-word widget" (Jan 10,  7:53pm)
References: <20160110003758.GA28696@tarsus.local2> 
	<160110091744.ZM585@torch.brasslantern.com> 
	<20160110195323.GA23064@tarsus.local2>
To: zsh-workers@zsh.org
Subject: Re: backward-kill-shell-word widget
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jan 10,  7:53pm, Daniel Shahaf wrote:
}
} Bart Schaefer wrote on Sun, Jan 10, 2016 at 09:17:44 -0800:
} > 
} >     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.

If you don't kill the space, select-in-shell-word won't identify the
correct word on a repeated call.

Other problems I've noted with this approach are that multiple calls
add to the kill ring but do not append to CUTBUFFER, and that this
kills the whole word under the cursor not just the part to the left.

So it needs some work.