Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
NO_CASE_GLO (Re: history-search + a few new user question)
- X-seq: zsh-workers 22051
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: NO_CASE_GLO (Re: history-search + a few new user question)
- Date: Mon, 05 Dec 2005 16:33:51 +0000
- In-reply-to: <20051205103021.0828ce8f.pws@xxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20051204162658.GA17541@xxxxxxxxxxxxxxxxxxx> <1051205063532.ZM22228@xxxxxxxxxxxxxxxxxxxxxxx> <20051205103021.0828ce8f.pws@xxxxxxx>
[redirected to zsh-workers]
On Dec 5, 10:30am, Peter Stephenson wrote:
}
} Well, there's the option "nocaseglob", which interprets patterns that
} way, but the problem is "downloads" is a simple string which isn't
} treated as a pattern
Here's a possibly wacky and probably hard-to-implement idea:
GLOB_EVERYTHING
When this option is set, zsh attempts pattern matching on every word
on the command line (except the command name), even plain strings
containing no pattern metacharacters. Globbing of plain strings is
always performed as if all of NOMATCH, BAD_PATTERN, NULL_GLOB and
CSH_NULL_GLOB are unset.
This is mostly useful in combination with NO_CASE_GLOB or MARK_DIRS.
(I go back and forth on whether MARK_DIRS belongs with NOMATCH rather
than with CASE_GLOB.)
Possibly unwanted side-effects: If a directory contains the files
download Download DownLoad
then globbing the seemingly plain string "download" yields three words.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author