From: Ray Andrews <rayandrews@eastlink.ca>
To: "Lawrence Velázquez" <larryv@zsh.org>
Cc: zsh-users@zsh.org
Subject: Re: trivial question
Date: Mon, 5 Dec 2022 18:29:11 -0800 [thread overview]
Message-ID: <c1c68720-f566-5b5b-89b1-b86aa63d6048@eastlink.ca> (raw)
In-Reply-To: <bf7123f7-a150-42b7-bbdb-788cb5e85e8e@app.fastmail.com>
On 2022-12-05 18:12, Lawrence Velázquez wrote:
> A decent starting point is to assume that unquoted punctuation is
> special until you verify otherwise (assuming you don't actually
> want the special behavior). Even then you might as well quote it
> to avoid confusing your future self.
Sure, I quote almost everything anyway.
>
> Presumably you've internalized that "*" is a globbing character,
> so you wouldn't be confused if this printed a bunch of filenames:
>
> echo *.txt
I may as well admit it: I didn't know you could do that. Nuts, I just
never tried it. One echo's strings. And true to form:
$ echo no-such-file*
... returns nothing, just like my initial example.
>
> Once you know that "[" is also a globbing character, it should cease
> to be confusing. That said, remembering all the globbing characters
> can be a challenge, especially the ones you don't use regularly.
Ok, this opens the door to clarity. I just need to know when zsh is
going to attempt globbing and keep on the watch for that. * ? [] (but
only paired!) what else? Man! To think that I'm just learning this
now. It's been an educational day.
next prev parent reply other threads:[~2022-12-06 2:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-05 2:05 Ray Andrews
2022-12-05 2:52 ` Lawrence Velázquez
2022-12-05 5:20 ` Ray Andrews
2022-12-05 6:40 ` Lawrence Velázquez
2022-12-05 14:11 ` Ray Andrews
2022-12-06 2:12 ` Lawrence Velázquez
2022-12-06 2:29 ` Ray Andrews [this message]
2022-12-06 4:29 ` Bart Schaefer
2022-12-06 6:08 ` Lawrence Velázquez
2022-12-06 10:18 ` Roman Perepelitsa
2022-12-06 11:21 ` Peter Stephenson
2022-12-06 15:28 ` Ray Andrews
2022-12-06 18:53 ` Bart Schaefer
2022-12-07 0:02 ` Lawrence Velázquez
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=c1c68720-f566-5b5b-89b1-b86aa63d6048@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=larryv@zsh.org \
--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).