zsh not accepting commandline args at end of command

zsh not accepting commandline args at end of command

[Eric Smith]

Hi

What might be causing this error in zsh.

eric@apple:~$ echo $SHELL
/bin/bash
eric@apple:~$ ls /tmp -F
ssh-XXUIWy1q/  v235390/
eric@apple:~$ zsh
[eric@apple ~]  $ ls -F /tmp
ssh-XXUIWy1q/  v235390/

... and here is the problem:
[eric@apple ~]  $ ls /tmp -F
ls: -F: No such file or directory
/tmp:
ssh-XXUIWy1q  v235390

thanks

-- 
Eric Smith

Re: zsh not accepting commandline args at end of command

[Miek Gieben]

[On 19 Nov, @18:15, Eric wrote in "zsh not accepting commandline  ..."]
> Hi
> 
> What might be causing this error in zsh.
> 
> eric@apple:~$ echo $SHELL
> /bin/bash
> eric@apple:~$ ls /tmp -F
> ssh-XXUIWy1q/  v235390/
> eric@apple:~$ zsh
> [eric@apple ~]  $ ls -F /tmp
> ssh-XXUIWy1q/  v235390/
> 
> ... and here is the problem:
> [eric@apple ~]  $ ls /tmp -F
> ls: -F: No such file or directory
> /tmp:
> ssh-XXUIWy1q  v235390
> 
> thanks

I don't have that problem here:
% ls /tmp -F
0007300254/           iceauth.XXXXB8AEpM  ksocket-miekg/  texXL9vHn
....

running zsh 4.0.7

Maybe you have some sort of weird alias for ls?

grtz Miek

Re: zsh not accepting commandline args at end of command

[Clint Adams]

> What might be causing this error in zsh.
> 
> eric@apple:~$ echo $SHELL
> /bin/bash
> eric@apple:~$ ls /tmp -F
> ssh-XXUIWy1q/  v235390/
> eric@apple:~$ zsh
> [eric@apple ~]  $ ls -F /tmp
> ssh-XXUIWy1q/  v235390/
> 
> ... and here is the problem:
> [eric@apple ~]  $ ls /tmp -F
> ls: -F: No such file or directory
> /tmp:
> ssh-XXUIWy1q  v235390

Is your PATH different under zsh (thus causing you to use a different
ls)?  Is something setting the environment variable POSIXLY_CORRECT?
Do you have different aliases for ls?

Re: zsh not accepting commandline args at end of command

[Peter Stephenson]

Eric Smith wrote:
> eric@apple:~$ ls /tmp -F
> ssh-XXUIWy1q/  v235390/

This is apparently the GNU ls behaviour.  (I think it's pretty yukky, but
never mind.)

> [eric@apple ~]  $ ls /tmp -F
> ls: -F: No such file or directory

This is standard with many other variants of ls.

Are the paths different in zsh and bash?

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: zsh not accepting commandline args at end of command

[Bart Schaefer]

On Nov 19,  6:15pm, Eric Smith wrote:
} 
} What might be causing this error in zsh.

I suspect you have an alias, or function wrapper, for 'ls'.  Works for me
with 'zsh -f'.

Re: zsh not accepting commandline args at end of command

[Eric Smith]

Thanks

But is weems to be using the same ls
[eric@apple ~]  $ which ls
/bin/ls
[eric@apple ~]  $ /bin/ls /tmp -F
/bin/ls: -F: No such file or directory
/tmp:
ssh-XXUIWy1q  v235390
[eric@apple ~]  $ exit

now in bash:
eric@apple:~$ /bin/ls /tmp -F
ssh-XXUIWy1q/  v235390/


Peter Stephenson said:
> Eric Smith wrote:
> > eric@apple:~$ ls /tmp -F
> > ssh-XXUIWy1q/  v235390/
> 
> This is apparently the GNU ls behaviour.  (I think it's pretty yukky, but
> never mind.)
> 
> > [eric@apple ~]  $ ls /tmp -F
> > ls: -F: No such file or directory
> 
> This is standard with many other variants of ls.
> 
> Are the paths different in zsh and bash?
> 
> -- 
> Peter Stephenson <pws@csr.com>                  Software Engineer
> CSR Ltd., Science Park, Milton Road,
> Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070
> 
> 
> **********************************************************************
> This email and any files transmitted with it are confidential and
> intended solely for the use of the individual or entity to whom they
> are addressed. If you have received this email in error please notify
> the system manager.
> 
> This footnote also confirms that this email message has been swept by
> MIMEsweeper for the presence of computer viruses.
> 
> www.mimesweeper.com
> **********************************************************************

-- 
Eric Smith

Re: zsh not accepting commandline args at end of command

[Eric Smith]

Nope according to this:
[eric@apple ~]  $ which ls
/bin/ls
[eric@apple ~]  $ ls /tmp -f
ls: -f: No such file or directory
/tmp:
ssh-XXUIWy1q  v235390
[eric@apple ~]  $ exit

back to bash:
eric@apple:~$ which ls
/bin/ls
eric@apple:~$ ls /tmp -f
./  ../  .X11-unix/  .font-unix/  ssh-XXUIWy1q/  .X0-lock  v235390/

Some differences in strace FWIW:

zsh:
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff8cc, 30, (nil), 0}) = 0
brk(0)                                  = 0x805774c
brk(0x807874c)                          = 0x807874c
brk(0)                                  = 0x807874c
brk(0x8079000)                          = 0x8079000
ioctl(1, SNDCTL_TMR_TIMEBASE, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, 0x5413, {ws_row=48, ws_col=126, ws_xpixel=1022, ws_ypixel=766}) = 0
stat64("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0
stat64("-f", 0x8057898)                 = -1 ENOENT (No such file or directory)
lstat64("-f", 0x8057898)                = -1 ENOENT (No such file or directory)
write(2, "ls: ", 4ls: )                 = 4
write(2, "-f", 2-f)                     = 2

bash:
_sysctl({{CTL_KERN, KERN_VERSION}, 2, 0xbffff9ac, 30, (nil), 0}) = 0
brk(0)                                  = 0x805774c
brk(0x807874c)                          = 0x807874c
brk(0)                                  = 0x807874c
brk(0x8079000)                          = 0x8079000
ioctl(1, SNDCTL_TMR_TIMEBASE, {B38400 opost isig icanon echo ...}) = 0
ioctl(1, 0x5413, {ws_row=48, ws_col=126, ws_xpixel=1022, ws_ypixel=766}) = 0
stat64("/tmp", {st_mode=S_IFDIR|S_ISVTX|0777, st_size=4096, ...}) = 0
open("/dev/null", O_RDONLY|O_NONBLOCK|O_DIRECTORY) = -1 ENOTDIR (Not a directory)
open("/tmp", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 3

Bart Schaefer said:
> On Nov 19,  6:15pm, Eric Smith wrote:
> } 
> } What might be causing this error in zsh.
> 
> I suspect you have an alias, or function wrapper, for 'ls'.  Works for me
> with 'zsh -f'.

-- 
Eric Smith

Re: zsh not accepting commandline args at end of command

[Aidan Kehoe]

 Ar an 19ú lá de mí 11, scríobh Eric Smith :

 > [eric@apple ~]  $ which ls
 > /bin/ls
 > [eric@apple ~]  $ /bin/ls /tmp -F
 > /bin/ls: -F: No such file or directory
 > /tmp:
 > ssh-XXUIWy1q  v235390
 > [eric@apple ~]  $ exit
 > 
 > now in bash:
 > eric@apple:~$ /bin/ls /tmp -F
 > ssh-XXUIWy1q/  v235390/

It's just about possible that Bash is using a global alias for ls. Aliases
don't show up in the output of "which" in Bash; if you want to see any
aliases for ls in Bash, try "alias" on its own. 

-- 
"... like, did you know, in Egypt, if a particularly beautiful girl, or the 
wife of a lord or whatever died, they wouldn't send her to the embalmer for 
three days? They'd let her spoil in the heat first."

Re: zsh not accepting commandline args at end of command

[Peter Stephenson]

Eric Smith wrote:
> Thanks
> 
> But is weems to be using the same ls
> [eric@apple ~]  $ which ls
> /bin/ls
> [eric@apple ~]  $ /bin/ls /tmp -F
> /bin/ls: -F: No such file or directory
> /tmp:
> ssh-XXUIWy1q  v235390
> [eric@apple ~]  $ exit
> 
> now in bash:
> eric@apple:~$ /bin/ls /tmp -F
> ssh-XXUIWy1q/  v235390/

In that case, you probably have POSIXLY_CORRECT set in the environment
for zsh.

% POSIXLY_CORRECT= =ls . -F
/home/pws/solaris8/bin/ls: -F: No such file or directory
.:
Master-16-14-bc2x.xcd  msg.html
% =ls . -F
Master-16-14-bc2x.xcd  msg.html

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

This footnote also confirms that this email message has been swept by
MIMEsweeper for the presence of computer viruses.

www.mimesweeper.com
**********************************************************************

Re: zsh not accepting commandline args at end of command

[William H. Magill]

On 19 Nov, 2003, at 12:32, Eric Smith wrote:
> But is weems to be using the same ls
> [eric@apple ~]  $ which ls
> /bin/ls
> [eric@apple ~]  $ /bin/ls /tmp -F
> /bin/ls: -F: No such file or directory
> /tmp:
> ssh-XXUIWy1q  v235390
> [eric@apple ~]  $ exit
>
> now in bash:
> eric@apple:~$ /bin/ls /tmp -F
> ssh-XXUIWy1q/  v235390/

The command results from bash are simply wierd.

Using
GNU bash, version 2.05b.0(1)-release (powerpc-apple-darwin7.0)

ls /tmp -F
generates exactly the same output as does  zsh or tcsh  (all without 
initialization files).
               ls: -F: No such file or directory

The command syntax is
                ls [-ABCFGHLPRTWZabcdfghiklmnopqrstuwx1] [file ...]

The parameters are positional, with the options first and the operands 
second.
The "-F" is treated as a file name, hence "no such file."

This is true for both the BSD and SystemV versions of ls.


T.T.F.N.
William H. Magill
# Beige G3 - Rev A motherboard - 768 Meg
# Flat-panel iMac (2.1) 800MHz - Super Drive - 768 Meg
# PWS433a [Alpha 21164 Rev 7.2 (EV56)- 64 Meg]- Tru64 5.1a
magill@mcgillsociety.org
magill@acm.org
magill@mac.com

Re: zsh not accepting commandline args at end of command

[Julien CROUZET]

> The command syntax is
>                 ls [-ABCFGHLPRTWZabcdfghiklmnopqrstuwx1] [file ...]
>
> The parameters are positional, with the options first and the operands
> second.
> The "-F" is treated as a file name, hence "no such file."
>
> This is true for both the BSD and SystemV versions of ls.
>

My thought : ls uses getopt(3)

Extract from man getopt(3) :
ENVIRONMENT VARIABLES
  POSIXLY_CORRECT
  If this is set, then option processing stops as soon as a non-option
argument is encountered.
--
Julien CROUZET