zsh-users
 help / color / mirror / code / Atom feed
From: Oliver Kiddle <opk@u.genie.co.uk>
To: zsh-users@sunsite.auc.dk
Subject: Re: New user questions
Date: Thu, 30 Mar 2000 12:12:47 +0100	[thread overview]
Message-ID: <38E336AF.C58B0A47@u.genie.co.uk> (raw)
In-Reply-To: <38E2E5BC.F4A8CB2B@inka.de>

Friedrich Dominicus wrote:

> > Changing separators
> > -------------------
> >
> > All the editor commands define a word separator as a space.  Is there a
> > way of changing zsh's idea of word separators?  I would prefer that it
> > consider '/' to be a separator as well.
> 
> guess zsh makes this automatically. But don't know

Zsh's idea of word separators is defined by the WORDCHARS parameter. It
actually defines characters to be considered part of a word as opposed
to separators. You can remove slash from it:

WORDCHARS="${WORDCHARS:s@/@}"

Personally, I only want slash to be considered a word separator for
moving and deleting words backward and forward - not for other things
like copying the last word so I define my own functions for these which
all look something like this:

tcsh-backward-word() {
  local WORDCHARS="${WORDCHARS:s@/@}"
  zle backward-word
}

Then I can do:
zle -N tcsh-backward-word
bindkey "..." tcsh-backword-word

Oliver Kiddle


  reply	other threads:[~2000-03-30 11:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-30  3:14 Andrew Morton
2000-03-30  5:20 ` Chmouel Boudjnah
2000-03-30  5:27 ` Friedrich Dominicus
2000-03-30 11:12   ` Oliver Kiddle [this message]
2000-03-30  6:50 ` Andrej Borsenkow
2000-03-30 18:22   ` Chmouel Boudjnah
2000-03-31  6:40     ` Andrew Morton
2000-03-31  7:45       ` Andrej Borsenkow
2000-03-31 10:33         ` Andrew Morton
2000-04-01 17:13       ` Zefram
2000-03-30  6:57 ` Andrej Borsenkow
2000-03-30 13:27 ` Zefram
2000-03-31 16:18   ` Bart Schaefer
2000-03-31  7:42 Sven Wischnowsky
2000-03-31 10:42 ` Andrew Morton

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=38E336AF.C58B0A47@u.genie.co.uk \
    --to=opk@u.genie.co.uk \
    --cc=zsh-users@sunsite.auc.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).