From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27839 invoked by alias); 10 Nov 2013 18:56:17 -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: 31949 Received: (qmail 14132 invoked from network); 10 Nov 2013 18:56:11 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 From: Bart Schaefer Message-id: <131110105603.ZM21496@torch.brasslantern.com> Date: Sun, 10 Nov 2013 10:56:03 -0800 In-reply-to: Comments: In reply to Martin Vaeth "Install run-help and *.zwc files system wide in build system" (Nov 10, 8:57am) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: Install run-help and *.zwc files system wide in build system MIME-version: 1.0 Content-type: text/plain; charset=us-ascii On Nov 10, 8:57am, Martin Vaeth wrote: } } The "documented way" to produce the files for run-help is only } suboptimal, because: } } 2. It does not work out-of-the box: With current man/groff versions, } one must export (an empty) GROFF_NO_SGR, MANWIDTH=80, possibly } unset MANPL, MANROFFSEQ, set utf8-aware locales etc. Of course the "right" way to go about this would be to generate the run-help files directly from the yodl source, or at least to generate formatted output from the yodl that could more easly be split up by Util/helpfiles. That would mean creating a "zhelp.yo" file patterned after Doc/zman.yo and Doc/ztexi.yo plus Makefile.in rules using "yodl -w zhelp.yo ..." } (b) Similarly, it would be nice if zsh would be able to } install *.zwc files for the functions it provides in the } build process. Someone should do (again? I wonder if it ever was done) benchmarking of whether .zwc files really save any time/CPU. I'm sure they do for sets of functions that are all going to be used during the session; but I'm doubtful that packing a bunch of autoloads, most of which are never actually loaded, into one big library file, is more effective than reading the individual files of only the subset that is used. It certainly doesn't save disk space; in nearly all cases ZWC files are bigger than their text counterparts, because they have to retain the original text for XTRACE purposes and no compression is applied. } Of course, both should happen only if appropriate ./configure } options are passed (e.g. compiling *.zwc files is only possible } in the build process if no cross-compilation is happening, } and building help-files requires tools like man, groff, and perl } which one should not require just to _build_ a zsh). This is why the precompiled doc is distributed in a separate tarball from the shell sources. If we're going to start building run-help files (or special Util/helpfiles input) as well, then those will need to be added to the doc tarball.