From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: tilde syntax
Date: Thu, 4 Jan 2024 18:03:10 -0800 [thread overview]
Message-ID: <dbdf7d7d-0f71-41fd-b938-d5ac4036e4a8@eastlink.ca> (raw)
In-Reply-To: <3adba5e1-18b6-495e-bcbc-09a554465029@app.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1047 bytes --]
On 2024-01-04 17:41, Lawrence Velázquez wrote:
> Another important part occurs earlier in "Parameter Expansion" and
> can admittedly be hard to find:
Yes. Seems almost inevitable that with such terse syntax normal search
culture is going to be frustrating. One must master the shell's jargon.
I wonder if a syntax index could be contemplated, it would look rather
strange:
$(
$((
$~
${~
if[
if[[
... every last construction.
> This is why you can use $~foo instead of ${~foo} sometimes.
I've noticed that but I don't even try to understand it. I am in awe of
the
geniuses who wrote the parser. The list of ifs, ands, buts and maybes is
not for a mere mortal to understand. That's what accretion gets you --
couldn't
be otherwise.
> That just refers to the result of the parameter expansion being
> subsequently used as something other than a literal value, if the
> context calls for it.
God knows. It's a steep hill to climb if you're not familiar with it.
Anyway I'm
at least alert to the issue.
Tx.
>
>
[-- Attachment #2: Type: text/html, Size: 2342 bytes --]
next prev parent reply other threads:[~2024-01-05 2:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 22:31 Ray Andrews
2024-01-04 22:49 ` Bart Schaefer
2024-01-04 23:04 ` Ray Andrews
2024-01-04 23:40 ` Lawrence Velázquez
2024-01-05 0:12 ` Ray Andrews
2024-01-05 1:41 ` Lawrence Velázquez
2024-01-05 2:03 ` Ray Andrews [this message]
2024-01-05 14:41 ` Mark J. Reed
2024-01-05 16:42 ` Ray Andrews
2024-01-05 19:58 ` Bart Schaefer
2024-01-05 22:50 ` Ray Andrews
2024-01-05 23:27 ` Bart Schaefer
2024-01-05 23:47 ` Ray Andrews
2024-01-06 0:23 ` Bart Schaefer
2024-01-06 3:44 ` Ray Andrews
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=dbdf7d7d-0f71-41fd-b938-d5ac4036e4a8@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).