zsh-users
 help / color / mirror / code / Atom feed
From: "William H. Magill" <magill@mcgillsociety.org>
To: Eric Smith <es@fruitcom.com>
Cc: zsh users <zsh-users@sunsite.dk>
Subject: Re: zsh not accepting commandline args at end of command
Date: Wed, 19 Nov 2003 22:31:09 -0500	[thread overview]
Message-ID: <FB740031-1B09-11D8-88D4-000393768D2C@mcgillsociety.org> (raw)
In-Reply-To: <20031119173206.GD31842@fruitcom.com>

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


  parent reply	other threads:[~2003-11-20  3:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-19 17:15 Eric Smith
2003-11-19 17:23 ` Miek Gieben
2003-11-19 17:26 ` Clint Adams
2003-11-19 17:26 ` Peter Stephenson
2003-11-19 17:32   ` Eric Smith
2003-11-19 17:53     ` Aidan Kehoe
2003-11-19 18:42     ` Peter Stephenson
2003-11-20  3:31     ` William H. Magill [this message]
2003-11-20 17:13       ` Julien CROUZET
2003-11-19 17:31 ` Bart Schaefer
2003-11-19 17:42   ` Eric Smith

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=FB740031-1B09-11D8-88D4-000393768D2C@mcgillsociety.org \
    --to=magill@mcgillsociety.org \
    --cc=es@fruitcom.com \
    --cc=zsh-users@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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