From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-users@sunsite.auc.dk
Subject: Re: zle questions
Date: Thu, 30 Mar 2000 12:38:45 +0200 (MET DST) [thread overview]
Message-ID: <200003301038.MAA28818@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: jean-baptiste.marchand@epita.fr's message of 30 Mar 2000 12:02:57 +0200
jean-baptiste.marchand wrote:
> 1)
>
> I like the menu completion feature (not complist) but I've still
> haven't found how to stop the completion when I've found the file I'm
> interested in :
>
> mylogin@mymachine ~> ls /
>
> then TAB
>
> and zsh cycles trough the directories of /
>
> If I choose /usr, I would like to hit a key to tell zsh to stop the
> completion, put /usr/ on the command-line and continue the menu
> completion in /usr
You just hit whatever key you want (`/' in this case) and that will
stop menucompletion. The `/' is this example is a bit magic (with the
AUTO_REMOVE_SLASH option set): if the completion code automatically
inserted the trailing `/' (as it normally does) and you hit `/' this
doesn't seem to change the command line. But what really happens is
that `/' is one of the characters that automatically remove the
inserted slash and then self-insert inserts it again.
> I thought the zle function accept-and-menu-complete could do the job
> but instead, it inserts the current completion followed by a space...
>
> 2) Is it possible in zle to specify word boundaries when using
> backward-kill-word ?
>
> In GNU Bash, you can do the following :
>
> mylogin@mymachine ~> ls /usr/X11R6/bin
>
> and if you want to execute 'ls' in '/usr/X11R6/' instead of
> '/usr/X11R6/bin', you would hit ^W and it would kill the word '/bin'.
> Instead, Zsh kills the whole '/usr/X11R6/bin'. It is because GNU Bash
> recognizes '/' as a word boundary by default.
>
> I found this feature quite interesting but maybe there is another way
> to do this easily.
The zle widgets for word movement/killing/whatever should all use the
$WORDCHARS special parameter. That gives the characters that are
normally considered to be part of a word (sans the alphanumeric ones
which are always considered to be part of words) -- and normally it
contains the slash. So you can just remove all characters from
$WORDCHARS where you want the cursor to be moved to or where you want
the word killing function to kill to.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2000-03-30 10:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-30 10:38 Sven Wischnowsky [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-03-30 10:02 jean-baptiste.marchand
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=200003301038.MAA28818@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--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).