From: Cameron Simpson <cs@zip.com.au>
To: Rich Boyce <rich@ebi.ac.uk>
Cc: Community support for Fedora users
<users@lists.fedoraproject.org>,
zsh-users@zsh.org
Subject: Re: zsh: bad option, bash works
Date: Tue, 20 Dec 2011 11:46:51 +1100 [thread overview]
Message-ID: <20111220004651.GA2311@cskk.homeip.net> (raw)
In-Reply-To: <4EEF2F30.7090404@ebi.ac.uk>
[ CC'd to zsh-users@zsh.org. My apologies for this. - Cameron ]
On 19Dec2011 12:33, Rich Boyce <rich@ebi.ac.uk> wrote:
| On 18/12/11 22:11, Cameron Simpson wrote:
| >On 18Dec2011 22:51, Zind<wzmindlog@gmail.com> wrote:
| >| Thanks a trillion. :-)
| >
| >Did you consult the manual? "man "zshbuiltins" says:
|
| Hmm. If you're unaware that type is a builtin, when using zsh 'man
| type' actually gives me BASH_BUILTINS(1).
That is a bit of a clue right there.
| If I don't know what a
| builtin is, and read about type in there, it tells me that '-t' is a
| valid option.
Indeed. There's no particular clue that the options don't work for all
shells.
| Perhaps when you do 'man type' or any other of the builtins, you
| should be shown the man page for the shell you're actually using?
Ugh. Via the normal man command? Please not. Via some shell builtin (:-)
alias? Maybe, provided it has big flashing lwaning lights and an
indicator of how to get the "real" manual entry.
Better, maybe, would be a "help" builtin for bash, zsh etc that
documented builtins and other topics, and offered to divert to "man"
as well (or on no hit).
Hmm. I see "bash" has a help comment. Zsh doesn't.
Cheers,
--
Cameron Simpson <cs@zip.com.au> DoD#743
http://www.cskk.ezoshosting.com/cs/
Clymer's photographs of this procedure show a very clean head. This is a lie.
There is oil in here, and lots of it. - Mike Mitten, rec.moto, 29sep1993
next parent reply other threads:[~2011-12-20 0:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4EEF2F30.7090404@ebi.ac.uk>
2011-12-20 0:46 ` Cameron Simpson [this message]
2011-12-20 3:54 ` Phil Pennock
2011-12-20 12:03 ` Rich Boyce
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=20111220004651.GA2311@cskk.homeip.net \
--to=cs@zip.com.au \
--cc=rich@ebi.ac.uk \
--cc=users@lists.fedoraproject.org \
--cc=zsh-users@zsh.org \
/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).