Re: emulate bash key bindings

[Peter Stephenson <p.stephenson@xxxxxxxxxxx>]

On Fri, 2020-01-10 at 09:51 +0000, Peter Stephenson wrote:
> On Fri, 2020-01-10 at 03:46 +0300, Andrey Butirsky wrote:
> > 
> > On 09.01.2020 17:29, Peter Stephenson wrote:
> > > 
> > > 
> > > On Thu, 2020-01-09 at 17:18 +0300, Andrey Butirsky wrote:
> > > > 
> > > > 
> > > > On 08.01.2020 13:00, Peter Stephenson wrote:
> > > > > 
> > > > > 
> > > > > zstyle ':zle:backward-kill-space-word:*' word-style space
> > > > Is the asterisk here '...:*' needed for something?
> > > Safety.  Contexts get added to with more specific information.
> > > Some examples are given later in the zshcontrib manual.  Even
> > > if you never use them, this will still work.
> > Is it me who intended to add to that context for my widgets, or it can 
> > be changed implicitly somehow?
>
> The point is there are contributed widgets that test with a context
> ":zle:name-of-widget:some-other-stuff".  I haven't looked to see
> if you're likely to encounter them in what you're doing, but it's
> easy to be sure you're not going to fall foul of that.

I just looked at the code...

Actually, I'm wrong and in generally you *don't* want that stuff.

I need it in my case because I'm using the ridiculously over the top
word-context style (which I suspect no one else has ever used).  *This*
gives you a subcontext.  Otherwise, you *don't* get an extra
subcomponent, so you need to leave out the ":*".  There is documentation
on word-context indicating this extra behaviour, but it isn't relevant
in your case, so I've just been confusing you, sorry.

Here's an example of the re-using a match widget for a specific style.

pws

diff --git a/Doc/Zsh/contrib.yo b/Doc/Zsh/contrib.yo
index d51fd518b..1e335d29d 100644
--- a/Doc/Zsh/contrib.yo
+++ b/Doc/Zsh/contrib.yo
@@ -2227,7 +2227,20 @@ is set in the context tt(:zle:*) to tt(true) if the word style is
 tt(bash) and tt(false) otherwise.  It may be overridden by setting it in
 the more specific context tt(:zle:forward-word*).
 
-Here are some examples of use of the styles, actually taken from the
+It is possible to create widgets with specific behaviour by defining
+a new widget implemented by the appropriate generic function, then
+setting a style for the context of the specific widget.  For example,
+the following defines a widget tt(backward-kill-space-word) using
+tt(backward-kill-word-match), the generic widget implmenting
+tt(backward-kill-word) behaviour, and ensures that the new widget
+always implements space-delimited behaviour.
+
+example(zle -N backward-kill-space-word backward-kill-word-match
+zstyle :zle:backward-kill-space-word word-style space)
+
+The widget tt(backward-kill-space-word) can now be bound to a 
+
+Here are some further examples of use of the styles, actually taken from the
 simplified interface in tt(select-word-style):
 
 example(zstyle ':zle:*' word-style standard
@@ -2251,7 +2264,7 @@ zstyle ':zle:transpose-words:whitespace' word-style shell
 zstyle ':zle:transpose-words:filename' word-style normal
 zstyle ':zle:transpose-words:filename' word-chars '')
 
-This provides two different ways of using tt(transpose-words) depending on
+This provides two different ways of using tt(transporse-words) depending on
 whether the cursor is on whitespace between words or on a filename, here
 any word containing a tt(/).  On whitespace, complete arguments as defined
 by standard shell rules will be transposed.  In a filename, only