From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: docs
Date: Fri, 28 Apr 2000 17:03:34 +0000 [thread overview]
Message-ID: <1000428170334.ZM24982@candle.brasslantern.com> (raw)
In-Reply-To: <200004281317.PAA22902@beta.informatik.hu-berlin.de>
On Apr 28, 3:17pm, Sven Wischnowsky wrote:
} Subject: PATCH: docs
}
}
} This mentions the `zcompile -z' trick for fans of KSH_AUTOLOAD in the
} compsys manual and moves the compctl section behind, err... after,
} err... to the err... compsys section.
Humph. I still think it reads better with the compctl section first,
if you're just reading through it like a book. There's very little
explanation in any of the completion sections about what completion
actually IS, and to have the first section be the one about writing
new widgets is putting the cart before the horse, IMO. And if you are
not reading it like a book, then it doesn't matter what order they're
in, does it?
Nevertheless, if you're going to insist on rearranging it, rearrange it
everywhere.
Index: Doc/Zsh/intro.yo
===================================================================
@@ -21,9 +21,9 @@
list(em(zshbuiltins) Zsh built-in functions)
list(em(zshzle) Zsh command line editing)
list(em(zshcompwid) Zsh completion widgets)
+list(em(zshcompsys) Zsh completion system)
list(em(zshcompctl) Zsh completion control)
list(em(zshmodules) Zsh loadable modules)
-list(em(zshcompsys) Zsh completion system)
list(em(zshzftpsys) Zsh built-in FTP client)
ifzshone(\
list(em(zshall) Meta-man page containing all of the above)
Index: Doc/Zsh/manual.yo
===================================================================
@@ -28,9 +28,9 @@
menu(Options)
menu(Shell Builtin Commands)
menu(Zsh Line Editor)
-menu(Completion Using compctl)
menu(Completion Widgets)
menu(Completion System)
+menu(Completion Using compctl)
menu(Zsh Modules)
menu(Zftp Function System)
@@ -98,14 +98,6 @@
menu(Completion)
menu(Miscellaneous)
-Completion Using compctl
-
-menu(Command Flags)
-menu(Option Flags)
-menu(Alternative Completion)
-menu(Extended Completion)
-menu(Example)
-
Completion Widgets
menu(Special Parameters)
@@ -121,6 +113,14 @@
menu(Bindable Commands)
menu(Completion Functions)
menu(Completion Directories)
+
+Completion Using compctl
+
+menu(Command Flags)
+menu(Option Flags)
+menu(Alternative Completion)
+menu(Extended Completion)
+menu(Example)
Zsh Modules
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~2000-04-28 17:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-28 13:17 Sven Wischnowsky
2000-04-28 17:03 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-10-05 14:06 Sven Wischnowsky
2000-10-05 8:38 Sven Wischnowsky
2000-10-05 13:53 ` Andrej Borsenkow
2000-01-07 14:49 Sven Wischnowsky
2000-01-07 19:22 ` Zefram
2000-01-08 20:17 ` Bart Schaefer
2000-01-08 20:21 ` Bart Schaefer
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=1000428170334.ZM24982@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).