From: ori@eigenstate.org
To: kernelloop@gmail.com
To: 9front@9front.org
Subject: Re: [9front] Re: filename expansion of rc
Date: Tue, 22 Dec 2020 08:30:33 -0800 [thread overview]
Message-ID: <5EFA8B556A9DD658ECAF9F7148166BDB@eigenstate.org> (raw)
In-Reply-To: <eb0808c3-ecc8-c6e7-ac3a-1ad3233002a3@gmail.com>
Quoth kl <kernelloop@gmail.com>:
> On 12/22/20 9:23 PM, kvik@a-b.xyz wrote:
> >> The character / must appear explicitly in a pattern, as must the first
> >> character of the path name components . and ..
> >
> > It means a glob won't expand into '/', '.', or '..'
>
> Will it expand into .name ?
cpu% touch .foo
cpu% ls .*
<no spoilers>
next prev parent reply other threads:[~2020-12-22 16:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-22 13:54 [9front] " kl
2020-12-22 14:52 ` [9front] " kl
2020-12-22 15:23 ` kvik
2020-12-22 15:38 ` kl
2020-12-22 16:30 ` ori [this message]
2020-12-22 18:25 ` Anthony Martin
2020-12-23 0:42 ` Alex Musolino
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=5EFA8B556A9DD658ECAF9F7148166BDB@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.org \
--cc=kernelloop@gmail.com \
/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.
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).