zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: "Sven Wischnowsky" <wischnow@informatik.hu-berlin.de>,
	<zsh-workers@sunsite.auc.dk>
Subject: Shuld it be so? RE: PATCH: Re: pws-10 RE: zsh-3.1.5-pws-9: _path_files  and symbolic links
Date: Thu, 4 Mar 1999 20:38:20 +0300	[thread overview]
Message-ID: <000501be6665$cb37bbb0$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903011445.PAA15418@beta.informatik.hu-berlin.de>


>
> Andrej Borsenkow wrote:
>
> > > The question is what one can find under `/u/'. If there is anything
> > > matching `l/l/T' the behavior might be correct (since it can't expand
> > > `u' to `usr' then).
> >
> > Nope. It is the problem of exact match. ``/u'' is matched _exactly_ and
> > hence ``/usr'' is never even tried.
>
> Ah, tricky. The patch below makes path components be left unchanged
> only if the rest of the string would produce a match below that
> directory.
>


(all patches applied):

bor@itsrm2:~%> l /u/l/m<TAB>
bor@itsrm2:~%> l /u1/lager-db/minileit.dbs/
u1/   usr/
^^^^^^^^^^ Somewhat strange. We really have /usr/lib/macros (and more), but
this list is a bit unexpected (well, at least I would expect then to first
menu complete ``/u1'' and ``/usr'' and then go on respectively)

And one more:

bor@itsrm2:~%> l /u/l/lib*X*<TAB>
  B-e-e-p

Is it not possible to complete glob patterns?

bor@itsrm2:~%> l -d  ~/s*
/home/bor/save/  /home/bor/src/

bor@itsrm2:~%> l /h/b/s*<TAB>
bor@itsrm2:~%> l /home/bor/s\*

but

bor@itsrm2:~%> l /h/b/s/*<TAB>
bor@itsrm2:~%> l /home/bor/save/*
save/  src/

the list is correct - it cycles through ``svae'' and ``src''

puzzled

/andrej


      reply	other threads:[~1999-03-04 17:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-01 14:45 Sven Wischnowsky
1999-03-04 17:38 ` 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='000501be6665$cb37bbb0$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.de \
    --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).