zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: _path_files and glob qualifiers
Date: Mon, 29 May 2000 11:54:33 +0200 (MET DST)	[thread overview]
Message-ID: <200005290954.LAA04335@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sun, 28 May 2000 18:14:51 +0000


Bart Schaefer wrote:

> zagzig[20] zstyle -L | grep completer
> zstyle ':completion:*' completer _oldlist _expand _complete _match _ignored _approximate _prefix
> 
> At first I thought the following was a problem with _expand:
> 
> zagzig[21] echo *zshenv(D)
> .zshenv zshenv
> zagzig[22] ls *zshenv(D)<TAB>
> zagzig[23] ls zshenv
> Completing corrections
> zshenv 
> Completing original
> *zshenv(D) 
> 
> Comparing an example that does work against the above via ^X?, I find that
> the real problem is that on line 305, _path_files tests [[ ! -o globdots ]]
> and therefore fails to generate dot-files as possible matches, even though
> the pattern includes the glob-dots qualifier.
> 
> A potential solution is to change [[ "$PREFIX" = .* ]] on lines 305 and 311
> to [[ "$PREFIX" = (.*|*\([^^]#D*\)) ]] or something like that, but I'm not
> entirely sure if that's correct (particularly when there is a suffix).  It
> might instead be necessary to test earlier and setopt localoptions globdots
> if the qualifier is spotted.

Hrm. Think of *(^.^D) and of *(^.,D) etc.

> But then there's the problem of generalizing to other qualifiers ...

Maybe when doing matching, we should copy all qualifiers from the line 
to the patterns used when generating matches (and remove the
qualifiers for matching purposes).

Bye
 Sven


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


             reply	other threads:[~2000-05-29  9:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-05-29  9:54 Sven Wischnowsky [this message]
2000-05-29 10:06 ` Bart Schaefer
  -- strict thread matches above, loose matches on Subject: below --
2000-05-28 18:14 Bart Schaefer

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=200005290954.LAA04335@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).