From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: Re: Some problem with completion matching
Date: Wed, 13 Dec 2000 16:42:12 +0000 [thread overview]
Message-ID: <1001213164213.ZM12168@candle.brasslantern.com> (raw)
In-Reply-To: <001a01c0651c$a32bf2f0$21c9ca95@mow.siemens.ru>
On Dec 13, 6:52pm, Andrej Borsenkow wrote:
}
} bor@itsrm2% l ntpd/*.c
} ntpd/check_y2k.c ntpd/map_vme.c
} ntpd/ntp_config.c ntpd/ntp_control.c
} ntpd/ntp_crypto.c ntpd/ntp_filegen.c
} ..... etc
} bor@itsrm2% l ntpd/.cTAB
} bor@itsrm2% l ntpd/ntpd.c
} Completing file
} ntpd.c version.c
}
} ???
}
} bor@itsrm2% zstyle -L
} zstyle ':completion:*' matcher-list '' 'm:{a-z}={A-Z}' 'm:{a-z}={A-Z}
} r:|[._-]=* r:|=*' 'm:{a-z}={A-Z} r:|[.-]=** r:|=**'
^^^^^^^^^^
I *think* the behavior you're seeing is correct, but Sven will have to
confirm. The match spec I marked means that file names are to split into
segments at dot, underscore, and hyphen, for purposes of matching. The
doc says that "... the anchor can occur anywhere, but must match in both
the command line and trial completion strings." Since there's only one
match for the anchor on the command line, only files having a single
such segment are eligible for completion.
I have a similar problem with my own matcher-list which I've been sort of
halfheartedly trying to work out for a while now. This example has made
me understand it better, but I still don't see a solution.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-12-13 16:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-13 15:52 Andrej Borsenkow
2000-12-13 16:42 ` Bart Schaefer [this message]
2000-12-14 7:18 Sven Wischnowsky
2000-12-14 8:29 ` 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=1001213164213.ZM12168@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).