From: kl <kernelloop@gmail.com>
To: 9front@9front.org
Subject: [9front] Re: filename expansion of rc
Date: Tue, 22 Dec 2020 20:52:20 +0600 [thread overview]
Message-ID: <3bb31cf8-d045-2884-e100-e74c23f5e0a3@gmail.com> (raw)
In-Reply-To: <7434204e-beb0-4123-ace3-7062785991f8@gmail.com>
I think it means that to expand to names beginning with . the character
`.` must be explicitly present.
But if i run the following in my home directory,
% printf '%s\n' *
I get this,
.bash_history
.bash_profile
.bashrc
.cache
.config
.env
.gnupg
.local
.password-store
.pki
.profile
.ssh
.vim
.viminfo
.vimrc
Documents
Downloads
Pictures
bin
d
n
t
Is this a bug?
next prev parent reply other threads:[~2020-12-22 14:59 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 ` kl [this message]
2020-12-22 15:23 ` [9front] " kvik
2020-12-22 15:38 ` kl
2020-12-22 16:30 ` ori
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=3bb31cf8-d045-2884-e100-e74c23f5e0a3@gmail.com \
--to=kernelloop@gmail.com \
--cc=9front@9front.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.
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).