zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Clint Adams <schizo@debian.org>, zsh-workers@sunsite.auc.dk
Subject: Re: run-help confused by whence output
Date: Sat, 18 Sep 1999 06:16:26 +0000	[thread overview]
Message-ID: <990918061626.ZM32739@candle.brasslantern.com> (raw)
In-Reply-To: <19990915134019.A13983@dman.com>

On Sep 15,  1:40pm, Clint Adams wrote:
} Subject: run-help confused by whence output
}
} run-help compadd brings up zshbuiltins(1) when compadd is described
} in zshcompwid(1).

This should help.  There are probably more builtins scattered in other
manual pages that I've missed, but I think this catches most of them.

I suppose it's possible that using comp* and zf* is too generic, but ...

Index: run-help
===================================================================
@@ -45,13 +45,23 @@
 	[[ ${what[(w)6]:t} != ${what[(w)1]} ]] && run-help ${what[(w)6]:t}
 	;;
     (*( is a * function))
-	builtin functions ${what[(w)1]} | ${=PAGER:-more}
-	;;
+	case ${what[(w)1]} in
+	(comp*) man zshcompsys;;
+	(zf*) man zshftpsys;;
+	(*) builtin functions ${what[(w)1]} | ${=PAGER:-more};;
+	esac;;
     (*( is a * builtin))
 	case ${what[(w)1]} in
 	(compctl) man zshcompctl;;
-	(bindkey) man zshzle;;
+	(comp*) man zshcompwid;;
+	(bindkey|vared|zle) man zshzle;;
 	(*setopt) man zshoptions;;
+	(cap|getcap|setcap) ;&
+	(clone) ;&
+	(ln|mkdir|mv|rm|rmdir|sync) ;&
+	(sched) ;&
+	(stat) man zshmodules;;
+	(zftp) man zshftpsys;;
 	(*) man zshbuiltins;;
 	esac
 	;;


-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com


      reply	other threads:[~1999-09-18  6:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-09-15 17:40 Clint Adams
1999-09-18  6:16 ` Bart Schaefer [this message]

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=990918061626.ZM32739@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=schizo@debian.org \
    --cc=zsh-workers@sunsite.auc.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).