zsh-workers
 help / color / mirror / code / Atom feed
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: _match still does not work in _path_files
Date: Tue, 2 Nov 1999 17:17:40 +0300	[thread overview]
Message-ID: <002801bf253d$05c20f60$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <199910180838.KAA25889@beta.informatik.hu-berlin.de>

> In a different message:
>
> > Ahem ... but why is menu completion started for the last path
> component in the
> > first place? I expect it to be started for
> {functions,functions.old} - the first
> > ambiguous part. And I bet it was - once.
> >
> > I tested it in zsh-3.1.6 and there _match works :-) and look what happens:
> >
> > itsrm2% l /t/s/z/f*/_<TAB>
> > itsrm2% l /tools/share/zsh/functions/_
> > functions/      functions.old/
> >
> > press TAB once more and selection is started for the first
> ambiguous component:
>
> This works for me again. If it still doesn't work for you, I need to
> know your compconfig.
>

Nope, it still does not work here. This is the ZSH from CVS of Tanaka Akira ...
quite recent, couple of hours (anybody know, how to find exact time when files
have been updated?)

Compare:

bor@itsrm2:/tools/src/zsh-cvs/zsh%> zsh -f
itsrm2% compinit -D
zsh: command not found: compinit
itsrm2% autoload -U compinit; compinit -D
itsrm2% bindkey -e
itsrm2% setopt nolistambiguous
itsrm2% {
cursh> compconf completer='_oldlist:_complete:_match'
cursh> compconf correct_accept='2n'
cursh> compconf correct_prompt='correct to:'
cursh> compconf dumpfile='/home/bor/.zcompdump'
cursh> compconf match_insert='unambig'
cursh> compconf match_original='yes'
cursh> compconf oldlist_list='_match'
cursh> compconf path_cursor='yes'
cursh> }
itsrm2% zmodload complist
itsrm2% SELECTMIN=0
itsrm2% ls /t/s/z/f*/_<TAB>
beeps

but

bor@itsrm2:/tools/src/db-2.7.7/build_unix%> zsh-3.1.6 -f
itsrm2% cd /tools/src/zsh-3.1.6/Completion
itsrm2% fpath=($PWD/*(/))
itsrm2% autoload -U compinit; compinit -D
itsrm2% {
cursh> compconf completer='_oldlist:_complete:_match'
cursh> compconf correct_accept='2n'
cursh> compconf correct_prompt='correct to:'
cursh> compconf dumpfile='/home/bor/.zcompdump'
cursh> compconf match_insert='unambig'
cursh> compconf match_original='yes'
cursh> compconf oldlist_list='_match'
cursh> compconf path_cursor='yes'
cursh> }
itsrm2% SELECTMIN=0
itsrm2% zmodload complist
itsrm2% bindkey -e
itsrm2% setopt nolistambiguous
itsrm2% ls /t/s/z/f*/_<TAB>
itsrm2% ls /tools/share/zsh/functions<CURSOR>/_
functions/      functions.old/

with TAB cycling between functions and functions.old

It is much worse actually; in the above setup as simple as

itsrm2% ls /t/s/z/f/_<TAB>

does not work - it beeps. In 3.1.6 pure I at least get both functions and
functions.old listed (I am still not quite happy with what happens after the
second TAB ...)



/andrej


  parent reply	other threads:[~1999-11-02 14:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-18  8:38 Sven Wischnowsky
1999-10-18  9:50 ` Bart Schaefer
1999-11-02 14:17 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-11-02 14:54 Sven Wischnowsky
1999-10-18 11:19 Sven Wischnowsky
1999-10-18  8:41 Sven Wischnowsky
1999-10-15 14:13 Sven Wischnowsky
1999-10-15 14:26 ` Andrej Borsenkow
1999-10-16 11:46 ` 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='002801bf253d$05c20f60$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).