From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: Globbing symlinks-to-${glob_qualifier}
Date: Wed, 18 Aug 2021 09:48:31 -0700 [thread overview]
Message-ID: <31f78c80-2cc8-db5f-659f-d9d27002781c@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7ZOsTw-XDSuL-dS15O3tkaCUtD1zHYooPteLnndKBoXmA@mail.gmail.com>
On 2021-08-18 8:24 a.m., Bart Schaefer wrote:
>
> You might be interested in cshnullglob.
>
This is a half baked musing as much as a question, but would it not be
inevitable that some of these glob options
nobareglobqual off
nocaseglob off
cshnullglob off
extendedglob on
noglob off
noglobalexport off
noglobalrcs off
globassign off
globcomplete off
globdots on
globstarshort on
globsubst off
kshglob off
nullglob on
numericglobsort off
shglob off
... must contradict each other? Options are always on/off, but wouldn't
the logic of some of these settings be more of a 'radio button' sort of
thing, where only one of several options can be active? I don't really
know but, for example, how can you combine shglob, kshglob, nullglob and
noglob? It would appear that they can't coexist.
next prev parent reply other threads:[~2021-08-18 16:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 3:27 Zach Riggle
2021-08-18 3:57 ` Daniel Shahaf
2021-08-18 4:02 ` Bart Schaefer
2021-08-18 13:10 ` Zach Riggle
2021-08-18 15:24 ` Bart Schaefer
2021-08-18 16:48 ` Ray Andrews [this message]
2021-08-18 17:23 ` Bart Schaefer
2021-08-18 17:55 ` Ray Andrews
2021-08-18 22:28 ` Which options are really doing anything (Re: Globbing symlinks-to-${glob_qualifier}) Bart Schaefer
2021-08-18 23:27 ` Ray Andrews
2021-08-19 2:32 ` Globbing symlinks-to-${glob_qualifier} Zach Riggle
2021-08-19 4:38 ` Lawrence Velázquez
2021-08-19 13:23 ` Daniel Shahaf
2021-08-19 13:25 ` Daniel Shahaf
2021-08-19 14:38 ` Ray Andrews
2021-08-19 13:54 ` Daniel Shahaf
2021-08-19 4:40 ` 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=31f78c80-2cc8-db5f-659f-d9d27002781c@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).