From: "Bart Schaefer" <schaefer@brasslantern.com>
To: John Beppu <beppu@ax9.org>, zsh-workers@sunsite.dk
Subject: zdoc (Re: A Completion Function for FIGlet)
Date: Wed, 20 Mar 2002 17:01:51 +0000 [thread overview]
Message-ID: <1020320170151.ZM25924@candle.brasslantern.com> (raw)
In-Reply-To: <20020320091931.GA29379@Ax9.org>
On Mar 20, 1:19am, John Beppu wrote:
}
} Many times, I've wished for a tool like perldoc. It could be called
} zdoc, and you'd be able to do things like:
}
} Reading about modifiers
} zdoc -m :q
} zdoc -m :r
}
} Reading about flags
} zdoc -F @
} zdoc -F U
}
} Reading about options
} zdoc -o promptsubst
}
} Reading about functions that come w/ the distribution
} zdoc -f _arguments
} zdoc -f _tags
}
} etc.
Try the commands
info zsh expansion history modifiers
info zsh expansion parameter
info zsh options description
info zsh "completion functions"
(Assuming you've installed the zsh info files, that is. And you do need
the quotes on the last one. Run `info standalone invoking' to find out
what is going on there.)
Also have a look at Util/helpfiles, which chops the zsh manual up into bits
and stuffs them in a directory where they can be accessed with the run-help
function (`autoload run-help'); then try using M-h in the middle of a zsh
command line. [Util/helpfiles could stand to be updated, it doesn't know
about the completion functions and user contributions sections, among other
things.]
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2002-03-20 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-20 9:19 A Completion Function for FIGlet John Beppu
2002-03-20 12:13 ` Oliver Kiddle
2002-03-20 22:55 ` John Beppu
2002-03-20 17:01 ` Bart Schaefer [this message]
2002-03-20 22:57 ` zdoc (Re: A Completion Function for FIGlet) John Beppu
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=1020320170151.ZM25924@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=beppu@ax9.org \
--cc=zsh-workers@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).