zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <borsenkow.msk@sni.de>
To: <zsh-workers@sunsite.auc.dk>
Subject: RE: PATCH: cleanup in zle_tricky.c
Date: Mon, 22 Mar 1999 20:45:22 +0300	[thread overview]
Message-ID: <003701be748b$c2b21740$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903221543.QAA18102@beta.informatik.hu-berlin.de>

>
> Question to others: do you see the same behavior Andrej does? I.e. is
> it me or is it the rest of the world who has run out of sync?
>

I know now where the problem(s) were - I sent this to Sven as well.

Bsically, the completion does not work with ambiguous prefix. In my case I
had /u1/informix* as well - that way _path_files took another branch.

In case of `.../*.suffix', the `/.*' was replaced by `/.', that 'course
could not match.

In case of x*y, first the whole was quoted (that gives you `x\*y') then *
was replaced by pattern, that should match anything except `/' - leaving
backslash inside. again, that pattern could not match.

bor@itsrm2:~%> sudo mkdir -p /foo/bar/baz
bor@itsrm2:~%> sudo touch /foo/bar/baz/{a,b,c}.h
bor@itsrm2:~%> l /foo/bar/baz/*.h
bor@itsrm2:~%> setopt globcomplete
bor@itsrm2:~%> l /foo/bar/baz/*.h
In both cases I completed /f/b/b/*.h

But

bor@itsrm2:~%> sudo mkdir -p /foo/baz
bor@itsrm2:~%> l /f/b/b/*.h
	Beep

cheers

/andrej

P.S. ZSH is fun, you know :-)


  reply	other threads:[~1999-03-22 17:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-22 15:43 Sven Wischnowsky
1999-03-22 17:45 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-24 12:29 Sven Wischnowsky
1999-03-23  9:51 Sven Wischnowsky
1999-03-24 10:41 ` Andrej Borsenkow
1999-03-22 15:29 Sven Wischnowsky
1999-03-22 14:28 Sven Wischnowsky
1999-03-22 15:32 ` Andrej Borsenkow
1999-03-22 13:55 Sven Wischnowsky
1999-03-22 14:09 ` Andrej Borsenkow
1999-03-22 14:17 ` Andrej Borsenkow
1999-03-22 10:56 Sven Wischnowsky
1999-03-22 13:02 ` 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='003701be748b$c2b21740$21c9ca95@mowp.siemens.ru' \
    --to=borsenkow.msk@sni.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).