zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: Re: _match still does not work in _path_files
Date: Mon, 18 Oct 1999 09:50:51 +0000	[thread overview]
Message-ID: <991018095051.ZM29043@candle.brasslantern.com> (raw)
In-Reply-To: <199910180838.KAA25889@beta.informatik.hu-berlin.de>

On Oct 18, 10:38am, Sven Wischnowsky wrote:
} Subject: RE: PATCH: Re: _match still does not work in _path_files
}
} The patch below implements some kind of mixed-matching style. Even
} with glob-complete behaviour it will try to match the prefix using the 
} match specs currently in effect. This is as far as we can get. Is it
} enough?

There's still one thing that bothers me; it's probably not related.  With
the default compconfig:

zagzig% cd /u/l/s/z/f/

Fails to complete to /usr/local/share/zsh/functions/.  The problem is
that _path_files wants there to be something after the final slash that
is a fragment of a directory name.  I vaguely recall some discussion of
a compconfig for something like this, but if there is one I can't find
it -- and given that "cd" doesn't care if the trailing slash is there,
shouldn't this work by default anyway?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


  reply	other threads:[~1999-10-18  9:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-18  8:38 Sven Wischnowsky
1999-10-18  9:50 ` Bart Schaefer [this message]
1999-11-02 14:17 ` Andrej Borsenkow
  -- strict thread matches above, loose matches on Subject: below --
1999-11-02 14:54 Sven Wischnowsky
1999-10-18 11:19 Sven Wischnowsky
1999-10-18  8:41 Sven Wischnowsky
1999-10-15 14:13 Sven Wischnowsky
1999-10-15 14:26 ` Andrej Borsenkow
1999-10-16 11:46 ` 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=991018095051.ZM29043@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).