zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: BUG: RE: What happened to _path_files?
Date: Mon, 11 Oct 1999 14:31:29 +0200 (MET DST)	[thread overview]
Message-ID: <199910111231.OAA03679@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Mon, 11 Oct 1999 15:25:13 +0400


Andrej Borsenkow wrote:

> It looks, like ambiguous completion does not work any more. It is not
> _path_files - it works correctly and compadd's all needed info. But for whatever
> reason completion C-code does not like it.

Only if the thing starts with a slash, right? The PREFIX parameter
wasn't set correctly.

Bye
 Sven

diff -u oldcompletion/Core/_path_files Completion/Core/_path_files
--- oldcompletion/Core/_path_files	Mon Oct 11 13:30:19 1999
+++ Completion/Core/_path_files	Mon Oct 11 14:30:01 1999
@@ -354,10 +354,10 @@
       # it as far as possible.
 
       if [[ "$tmp3" = */* ]]; then
-        PREFIX="${linepath}${cpre}${tmp3%%/*}"
+        PREFIX="${donepath}${linepath}${cpre}${tmp3%%/*}"
 	SUFFIX="/${tmp3#*/}"
       else
-        PREFIX="${linepath}${cpre}${tmp3}"
+        PREFIX="${donepath}${linepath}${cpre}${tmp3}"
 	SUFFIX=""
       fi
 

--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~1999-10-11 12:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-11 12:31 Sven Wischnowsky [this message]
1999-10-11 13:59 ` Andrej Borsenkow
1999-10-11 14:58   ` Prblems with _match and exact matches (was: RE: BUG: RE: What happened to _path_files?) Andrej Borsenkow
  -- strict thread matches above, loose matches on Subject: below --
1999-09-28 10:07 What happened to _path_files? Andrej Borsenkow
1999-10-11 11:25 ` BUG: " 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=199910111231.OAA03679@beta.informatik.hu-berlin.de \
    --to=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).