9front - general discussion about 9front
 help / color / mirror / Atom feed
* [9front] filename expansion of rc
@ 2020-12-22 13:54 kl
  2020-12-22 14:52 ` [9front] " kl
  2020-12-22 18:25 ` Anthony Martin
  0 siblings, 2 replies; 7+ messages in thread
From: kl @ 2020-12-22 13:54 UTC (permalink / raw)
  To: 9front

In Rc's (plan9port) man page there is,

The character / must appear explicitly in a pattern, as must the first 
character of the path name components .  and ..


What does this part means?

 > as must the first character of the path name components .  and ..

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [9front] Re: filename expansion of rc
  2020-12-22 13:54 [9front] filename expansion of rc kl
@ 2020-12-22 14:52 ` kl
  2020-12-22 15:23   ` kvik
  2020-12-22 18:25 ` Anthony Martin
  1 sibling, 1 reply; 7+ messages in thread
From: kl @ 2020-12-22 14:52 UTC (permalink / raw)
  To: 9front

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?


^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] Re: filename expansion of rc
  2020-12-22 14:52 ` [9front] " kl
@ 2020-12-22 15:23   ` kvik
  2020-12-22 15:38     ` kl
  0 siblings, 1 reply; 7+ messages in thread
From: kvik @ 2020-12-22 15:23 UTC (permalink / raw)
  To: 9front

> 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 '..'

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] Re: filename expansion of rc
  2020-12-22 15:23   ` kvik
@ 2020-12-22 15:38     ` kl
  2020-12-22 16:30       ` ori
  0 siblings, 1 reply; 7+ messages in thread
From: kl @ 2020-12-22 15:38 UTC (permalink / raw)
  To: 9front

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 ?

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] Re: filename expansion of rc
  2020-12-22 15:38     ` kl
@ 2020-12-22 16:30       ` ori
  0 siblings, 0 replies; 7+ messages in thread
From: ori @ 2020-12-22 16:30 UTC (permalink / raw)
  To: kernelloop, 9front

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>

^ permalink raw reply	[flat|nested] 7+ messages in thread

* [9front] Re: filename expansion of rc
  2020-12-22 13:54 [9front] filename expansion of rc kl
  2020-12-22 14:52 ` [9front] " kl
@ 2020-12-22 18:25 ` Anthony Martin
  2020-12-23  0:42   ` Alex Musolino
  1 sibling, 1 reply; 7+ messages in thread
From: Anthony Martin @ 2020-12-22 18:25 UTC (permalink / raw)
  To: 9front

kl <kernelloop@gmail.com> once said:
> In Rc's (plan9port) man page there is,
>
> [...]
>
> What does this part means?
>
> > as must the first character of the path name components .  and ..

It only matters for rc on Unix (and not under plan9port).
Plan 9 directories don't contain explicit entries for '.'
and '..', so those paths will never be subjected to file
name matching.

  Anthony

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: [9front] Re: filename expansion of rc
  2020-12-22 18:25 ` Anthony Martin
@ 2020-12-23  0:42   ` Alex Musolino
  0 siblings, 0 replies; 7+ messages in thread
From: Alex Musolino @ 2020-12-23  0:42 UTC (permalink / raw)
  To: 9front

I think the documentation is wrong/misleading, though.  By
my reading, we have to provide the *first* character of the
path name component '..' then .* should match '..' but it
doesn't.  I don't think the behaviour is wrong at all, just
the documentation (possibly).

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, other threads:[~2020-12-23  0:52 UTC | newest]

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-22 13:54 [9front] filename expansion of rc 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
2020-12-22 18:25 ` Anthony Martin
2020-12-23  0:42   ` Alex Musolino

9front - general discussion about 9front

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.vuxu.org/9front

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V1 9front 9front/ http://inbox.vuxu.org/9front \
		9front@9front.org
	public-inbox-index 9front

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.vuxu.org/vuxu.archive.9front


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git