From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
<zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: Re: General comments on completion
Date: Thu, 8 Jul 1999 17:20:32 +0400 [thread overview]
Message-ID: <000801bec944$a7d5ac30$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199907080904.LAA11932@beta.informatik.hu-berlin.de>
Maybe we should use a different config key for
> this -- if you are using _oldlist and find some strange behavior, tell
> me.
>
The following happens with _oldlist and the completion keys:
bor@itsrm2:~/test/match%> compconf -L
compconf correct_accept='2n'
compconf match_original='yes'
compconf completer='_oldlist:_complete:_match'
compconf dumpfile='/home/bor/.zcompdump'
compconf oldlist_list='_match'
compconf path_cursor='yes'
compconf match_insert='unambig'
compconf correct_prompt='correct to:'
bor@itsrm2:~/test/match%> ls /h/b/t/m/a?a/<12->TAB
bor@itsrm2:~/test/match%> ls /home/bor/test/match/a/\<12-\>
axa/ aya/ ^ cursor here; after TAB
bor@itsrm2:~/test/match%> l /home/bor/test/match/axa/\<12-\>CURSOR HERE
axa/ aya/ ^
It happens if _oldlist is used *and* cursor is initially at the end of word. If
I move cursor inside of word, it works as expected:
bor@itsrm2:~/test/match%> ls /h/b/t/m/a?a/<12->TAB
^ cursor here
bor@itsrm2:~/test/match%> ls /home/bor/test/match/a/\<12-\>
axa/ aya/ ^ cursor here
bor@itsrm2:~/test/match%> ls /home/bor/test/match/axa/\<12-\>
axa/ aya/ ^ cursor here
I have only setopt nolistambiguous explicitly set. It remains from old zshrc.
/andrej
next prev parent reply other threads:[~1999-07-08 13:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-07-08 9:04 Sven Wischnowsky
1999-07-08 13:20 ` Andrej Borsenkow [this message]
1999-07-08 14:20 Sven Wischnowsky
1999-07-08 15:53 ` Andrej Borsenkow
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='000801bec944$a7d5ac30$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@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).