gnu-arch-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Gnu-arch-users] arch's file naming scheme is shell unfriendly


From: Mikhael Goikhman
Subject: Re: [Gnu-arch-users] arch's file naming scheme is shell unfriendly
Date: Mon, 18 Oct 2004 15:54:45 +0000
User-agent: Mutt/1.4.2.1i

On 18 Oct 2004 10:51:20 -0400, Adrian Irving-Beer wrote:
> 
> On Sun, Oct 17, 2004 at 01:52:23PM +0000, Mikhael Goikhman wrote:
> 
> > To complete literal {substr} in a file name one should quote or backslash
> > it in zsh. Similarly with plain =files:
> > 
> >   % cd subdir/.arch-ids; ls -l =id
> >   -rwxr-xr-x  1 root root 16752 Mar 16  2004 /usr/bin/id
> 
> Don't know how our settings are different, but I don't see either
> behaviour (in zsh).
> 
> address@hidden:~/rc/.arch-ids% ls -l =id
> -rw-r--r--  1 wisq wisq 68 2004-10-13 16:38 =id

Any zsh I have with or without ~/.zsh* behaves as I wrote regarding =id:

  zsh 4.0.7 (alpha--netbsd)
  zsh 4.0.9 (i386-redhat-linux-gnu)
  zsh 4.2.1 (i686-pc-linux-gnu)

> address@hidden:~/rc/.arch-ids% cd ..
> address@hidden:~/rc% ls {arch}

You missed the word "to complete", please reread my sentence. But if you
speak about the result of your command, it highly depends on zsh options:

  % setopt braceexpand braceccl
  % ls {arch}
  ls: a: No such file or directory
  ls: c: No such file or directory
  ls: h: No such file or directory
  ls: r: No such file or directory

Regards,
Mikhael.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]