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: Prblems with _match and exact matches (was: RE: BUG: RE: What happened to _path_files?)
Date: Mon, 11 Oct 1999 18:58:58 +0400	[thread overview]
Message-ID: <000301bf13f9$252b6a90$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <000201bf13f0$c8991e60$21c9ca95@mow.siemens.ru>


>
> With my settings it is even worse:
>
> bor@itsrm2:~%> l /t/s/z/f/_<TAB>
> bor@itsrm2:~%> l /tools/share/zsh/functions/_<TAB>
> functions/      functions.old/
>

Just to make sure - the actual bug is, that cursor is moved to the end of word
and not to the end of ambiguous part (path_cursor). I just tried with
zsh-3.1.6-pws-3 - and there it is the same ... so, may be, it was there for a
long time.

It happens only if one match is a prefix of another (i.e. one match is exact)
and there is no exact match for suffix. With 3.1.6-pws-3 it does not happen with
_match:

itsrm2% l /t/s/z/f*/_<TAB>
itsrm2% l /tools/share/zsh/functions<CURSOR HERE>/_
functions/      functions.old/

but with 3.1.6-pws-6 + all current patches:

or@itsrm2:~%> l /t/s/z/f*/_<TAB>

just beeps.

If suffix is exact, that works as expected:

bor@itsrm2:~/test%> l ~/test/(ls|lss)
/home/bor/test/ls:
a     acc

/home/bor/test/lss:
a     acc

bor@itsrm2:~/test%> l /h/b/t/l/a<TAB>
bor@itsrm2:~/test%> l /home/bor/test/ls<CURSOR HERE>/a
ls/   lss/

It still works even in this case:

bor@itsrm2:~/test%> l ~/test/(ls|lss)
/home/bor/test/ls:
ab     acc

/home/bor/test/lss:
a     acc

But not in this

bor@itsrm2:~/test%> l ~/test/(ls|lss)
/home/bor/test/ls:
ab     acc

/home/bor/test/lss:
ab     acc

My setings in ~/.zshrc are:

ompconf completer=_oldlist:_complete:_match
compconf match_original=yes
compconf match_insert=unambig
compconf path_cursor=yes
compconf oldlist_list=_match
LS_COLORS=
SELECTMIN=0
setopt cdablevars
setopt extendedhistory
setopt extendedglob
setopt histexpiredupsfirst
setopt histignorealldups
setopt histignoredups
setopt histreduceblanks
setopt histsavenodups
setopt ignoreeof
setopt nobanghist
setopt nolistambiguous
setopt nolistbeep

/andrej


      reply	other threads:[~1999-10-11 14:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-11 12:31 BUG: RE: What happened to _path_files? Sven Wischnowsky
1999-10-11 13:59 ` Andrej Borsenkow
1999-10-11 14:58   ` Andrej Borsenkow [this message]

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='000301bf13f9$252b6a90$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).