From: <kazda@VNET.IBM.COM> (Mike Kazda)
To: Zefram <A.Main@dcs.warwick.ac.uk>
Cc: zsh-workers@math.gatech.edu
Subject: Re: kill-word & friends in ZLE
Date: Thu, 16 May 1996 10:56:18 -0400 [thread overview]
Message-ID: <9605161456.AA34688@rumor.fishkill.ibm.com> (raw)
In-Reply-To: <11210.199605152318@stone.dcs.warwick.ac.uk>
>>>>> "Zefram" == Zefram <A.Main@dcs.warwick.ac.uk> writes:
>> It is quite irritating for me that in zsh's Emacs mode
>> functions like backward-kill-word and similar behave in a
>> different fashion. Examples:
>>
>> fly% cd /usr/local/lib/gwembljh[Esc-Backspace]
>>
>> and everything is erased, instead of just gwembljh.
I've had this problem ever since switching to zsh and I never really
complained about it. But it is a big complaint of mine.
Zefram> The vi word functions (vi-{for,back}ward-word, etc.) are
Zefram> more like what you want. Or you could just modify
Zefram> WORDCHARS in your .zshrc.
I tried setting the following in zsh (beta17) and it had no effect:
WORDCHARS='*?_-.[]~=/&;!#$%^(){}<>'
Do you have any hints? I feel that the default behavior should work
like emacs or ksh using emacs mode. Meaning if you do
[Escape-Backspace] on something which has slashes in it (which I would do
all the time on pathnames that I mess up in typing) it should kill
only back to the next slash.
Mike
next prev parent reply other threads:[~1996-05-16 15:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-05-15 23:02 Hrvoje Niksic
1996-05-15 23:18 ` Zefram
1996-05-16 14:56 ` Mike Kazda [this message]
1996-05-16 17:09 ` Barton E. Schaefer
1996-05-15 23:47 ` Bart Schaefer
1996-05-16 1:12 ` Wayne Davison
[not found] ` <wayne@clari.net>
1996-05-16 0:49 ` Bart Schaefer
1996-05-16 22:17 ` Wayne Davison
1996-05-16 12:00 ` Hrvoje Niksic
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=9605161456.AA34688@rumor.fishkill.ibm.com \
--to=kazda@vnet.ibm.com \
--cc=A.Main@dcs.warwick.ac.uk \
--cc=zsh-workers@math.gatech.edu \
/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).