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: RE: PATCH: cleanup in zle_tricky.c
Date: Wed, 24 Mar 1999 13:41:23 +0300	[thread overview]
Message-ID: <001601be75e2$dc8c8d50$21c9ca95@mowp.siemens.ru> (raw)
In-Reply-To: <199903230951.KAA18666@beta.informatik.hu-berlin.de>

> >
> > 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.
>
> Ah, I thought you had made sure that this didn't happen because we had
> this discussion already -- and hence I didn't test for it (the real
> problem was that without globcomplete there were no matches). At that
> time I had asked if we wanted the path to expand as far as possible in
> such cases.
> Since you perceived this as a bug, the patch below makes the answer
> `yes'.
>
> > In case of `.../*.suffix', the `/.*' was replaced by `/.', that 'course
> > could not match.
>


I am sorry for this misunderstanding - obviously, I was not clear enough
-( What I intended to say, was:

the bug with .../*.suffix (* removal) happened (or had effect) only in case
of ambiguous prefix (at least so my test results). I did not mean anything
else.

Now, that I have been working with this a bit more, the result of this patch
is somewhat unexpected. Now, the /a/b/c/d expands the prefix even if nothing
would match. Returning to my expamle - the bug with /u/i/s/*.h was, that
this does match, but the match failed (because of bug). And current
/u/i/s/*.c -> /usr/include/sys/*.c is a bit too much ...

> Ok, with the patch below and the ones from 5871, 5872, and 5875: does
> everything work as you want (or expect ;-) it now? Including those
> `test/{a1,b1,x1y}' problems you mentioned?

Yes, with your great completers all works as expected - with above exeption.

May I suggest, that this change would be backed off? Probably, with
configuration option (but I fail to see, when it would be useful). If direct
completion of /a/b/c/d fails, this is the job for approximate/correcting
completion then.

To be more precise - the change makes prefix to be expanded even if nothing
matches. I did not intend it, and did not ask for it.

cheers

/andrej

P.S. Sorry for turmoil this week. But when after every patch I get different
results after pressing TAB ... :-)


  reply	other threads:[~1999-03-24 11:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-23  9:51 Sven Wischnowsky
1999-03-24 10:41 ` Andrej Borsenkow [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-03-24 12:29 Sven Wischnowsky
1999-03-22 15:43 Sven Wischnowsky
1999-03-22 17:45 ` 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='001601be75e2$dc8c8d50$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).