From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7150 invoked by alias); 26 Sep 2016 10:56:55 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 39442 Received: (qmail 16121 invoked from network); 26 Sep 2016 10:56:55 -0000 X-Qmail-Scanner-Diagnostics: from kahlil.inlv.org by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(37.59.109.123):SA:0(-3.1/5.0):. Processed in 0.459745 secs); 26 Sep 2016 10:56:55 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-3.1 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: martijn@inlv.org X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at inlv.org does not designate permitted sender hosts) Subject: Re: Is "command" working right, yet? To: Zsh hackers list References: <160202163744.ZM2066@torch.brasslantern.com> <56B761B8.6000507@inlv.org> <160925201328.ZM24563@torch.brasslantern.com> From: Martijn Dekker Message-ID: <19a1d587-2963-5dfb-9205-9c23198ca5b7@inlv.org> Date: Mon, 26 Sep 2016 11:56:42 +0100 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <160925201328.ZM24563@torch.brasslantern.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Op 26-09-16 om 04:13 schreef Bart Schaefer: > It's because "command" is a sort-of keyword instead of a builtin, I see. I guess that explains another bug I've noticed: if you quote the "command" command name to defeat a possible alias, it doesn't accept options at all, e.g.: % \command -V if zsh: command not found: -V Also, then this output: % command -V command command is a shell builtin seems a bit misleading. - Martijn