From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: color codes to eval
Date: Wed, 10 Apr 2024 17:15:49 -0700 [thread overview]
Message-ID: <7b369845-98d1-4b10-8b26-02049e40a041@eastlink.ca> (raw)
In-Reply-To: <02e80e14-471d-4084-9ba1-148aedd70443@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1206 bytes --]
On 2024-04-10 17:01, Lawrence Velázquez wrote:
> That's right. And since you're not using $~var or GLOB_SUBST, the
> result of that delayed expansion will be used literally instead of
> as a pattern for filename generation.
Ah! Yes, I've run aground on those rocks too. What would have served
me well, and avoided the majority of my questions here, is some Big Book
of Shell Gotchas. Especially useful for a guy like me coming from DOS
and only having that, and C, as my notions of what programming
environments are like. What's frustrating is that I learn something and
six months latter I've forgotten. I sure wish we could scan the
archives, I'd be going back and checking my own previous questions --
like just now, I knew I'd asked about '(q)' previously.
> If you can avoid it, you might as well. (Especially if you don't
> have a clear idea of what it does.)
I don't! All I know is that it got me into trouble.
> It's usually not what you want, since it may let typos and other
> mistakes go by quietly. It's generally easy enough to handle
> troublesome non-patterns by quoting them or using them through
> variables.
>
Yeah who needs that, when we have a proper fix above.
[-- Attachment #2: Type: text/html, Size: 2101 bytes --]
prev parent reply other threads:[~2024-04-11 0:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:46 Ray Andrews
2024-04-10 18:39 ` Lawrence Velázquez
2024-04-10 19:05 ` Andreas Kähäri
2024-04-10 19:17 ` Ray Andrews
2024-04-10 19:12 ` Ray Andrews
2024-04-11 0:01 ` Lawrence Velázquez
2024-04-11 0:15 ` Ray Andrews [this message]
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=7b369845-98d1-4b10-8b26-02049e40a041@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).