zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: Re: More fun with completion: glob qualifiers ignored for ignored-patterns style?
Date: Mon, 14 Jul 2003 21:39:40 +0000	[thread overview]
Message-ID: <1030714213940.ZM6927@candle.brasslantern.com> (raw)
In-Reply-To: <87n0fg3l1m.fsf@ceramic.fifi.org>

On Jul 14,  1:33pm, Philippe Troin wrote:
} Subject: More fun with completion: glob qualifiers ignored for ignored-pat
}
} % zstyle ':completion:*:all-files' ignored-patterns '*(/)'

The ignored-patterns style is not checked for the all-files tag, only for
the globbed-files tag in _files and the argument-rest tag in _normal.

However, even if you set it for the correct tag, it still won't work,
because it really is a _pattern_ (as in [[ string = pattern ]]) and not
a filesystem glob.  It can only match the string, not the file type.

} Is that because bare_glob_qual is unset when expanding the pattern?

So, no.

} By the way, the manual says about glob qualifiers:
} 
}    If the option BARE_GLOB_QUAL is set, then a trailing set of parentheses
}    containing no `|' or `(' characters (or `~' if it is special) is taken
}    as a set of glob qualifiers.
} 
} Does that mean that:
} 
}  - if BARE_GLOB_QUAL is set, glob qualifiers are enabled
} 
}  - if BARE_GLOB_QUAL is unset, glob qualifiers are disabled?

In 4.0.x, that's effectively what it means.  BARE_GLOB_QUAL was added in
anticipation of other qualifier syntax that had not been invented yet.

In 4.1.x, it means that if BARE_GLOB_QUAL is set, zsh uses a heuristic to
decide if a trailing parenthesized expression is a glob qualifier, and if
BARE_GLOB_QUAL is NOT set, you have to 'setopt EXTENDED_GLOB' and use an
explicit (#q) to introduce a qualifier.


  reply	other threads:[~2003-07-14 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-14 20:33 Philippe Troin
2003-07-14 21:39 ` Bart Schaefer [this message]
2003-07-15  1:57   ` Philippe Troin

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=1030714213940.ZM6927@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@sunsite.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).