zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: Word component characters -- how to have two behaviors?
Date: Tue, 16 Mar 2004 11:27:54 +0000	[thread overview]
Message-ID: <11963.1079436474@csr.com> (raw)
In-Reply-To: "Kai Grossjohann"'s message of "Tue, 16 Mar 2004 10:51:36 +0100." <878yi1jf13.fsf@emptyhost.emptydomain.de>

Kai Grossjohann wrote:
> kai-forward-word () {
>     select-word-style shell; zle forward-word; select-word-style bash;
> }
> zle -N kai-forward-word kai-forward-word
> bindkey "\eF" kai-forward-word
> 
> Is there a more elegant way to do this?

Yes, this is what styles are for.  The current syntax is:

  zle -N kai-forward-word forward-word-match
  bindkey '\eF' kai-forward-word
  zstyle ':zle:kai-forward-word' word-style shell

This creates and binds a new widget implemented by the same function as
the version of forward-word used when the word-style mechanism is in
effect.  `zle -lL | grep forward-word' would give you that information.

Then you set a style specifically for the new widget you created.  Any
of the styles described in zshcontrib for the *-match functions work.
As you can see, it's much neater because it's all done with names;
there's no new code.  It resembles a number of clever tricks in the
completion system (not coincidentally).

Actually, I've been thinking about extending the mechanism (there was a
discussion a while ago but no one responded), so it might be safer to
use

  zstyle ':zle:kai-forward-word(:*|)'

in case I add extra colon-delimited arguments.

(You can just about work this out, except that last suggestion, from a
combination of the zshzle, zshcontrib and zshutil manual pages, but it's
tough going.  I should add something like this as an example.)

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************


      reply	other threads:[~2004-03-16 13:37 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-16  9:51 Kai Grossjohann
2004-03-16 11:27 ` Peter Stephenson [this message]

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=11963.1079436474@csr.com \
    --to=pws@csr.com \
    --cc=zsh-users@sunsite.dk \
    /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).