zsh-users
 help / color / mirror / code / Atom feed
From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: trivial question
Date: Sun, 4 Dec 2022 21:20:54 -0800	[thread overview]
Message-ID: <ca5c08fc-d81a-5e2c-d8ac-d4c60926ecaf@eastlink.ca> (raw)
In-Reply-To: <63ae2364-1bba-405d-a1e6-4813df512340@app.fastmail.com>


On 2022-12-04 18:52, Lawrence Velázquez wrote:
> In this context, "var[2]" is recognized as a valid glob, and zsh
> attempts to generate filenames with it.  If a file or directory
> matches, its name is inserted as usual.
I see.  A file glob would be the last thing I'd be expecting, I'm 
expecting it to be a nothing but a string.  Anyway that's a clear 
explanation.

> % zsh +o NOMATCH foo.zsh
> 	<var[2]><ain't><nothing>
>
That works.  First experiments trying '(un)setopt NOMATCH' aren't 
working but now that I know what to chew on I'll bag it.
> This is all explained in the manual.
> https://zsh.sourceforge.io/Doc/Release/Expansion.html#Filename-Generation
>
>
Thanks, as is so often the case, it's not having a clue where to look 
that's that hard part.  I'd not have dreamed this was a filename 
generation issue.




  reply	other threads:[~2022-12-05  5:21 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 [this message]
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
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=ca5c08fc-d81a-5e2c-d8ac-d4c60926ecaf@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).