From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk (Zsh users list)
Subject: Re: installing zsh questions
Date: Mon, 13 Mar 2006 18:52:38 +0000 [thread overview]
Message-ID: <EXCHANGE037oFJyi0Gf00015a38@exchange03.csr.com> (raw)
In-Reply-To: <20060313181552.GA9806@let.rug.nl>
Francisco Borges wrote:
> Hello!
>
> Two possibly very silly questions about installing zsh locally:
> (BTW I'm running Debian "stable")
>
> 1. To make help files for run-help I used:
>
> % man -m /usr/local/man zshall | colcrt - | \
> perl ~/sys/zsh/zsh-4.3.1/Util/helpfiles
>
> But this created files like:
>
> A
> On
> By
> But
> No
> [etc]
I don't quite understand how this ever worked... the exit condition
when parsing zshall doesn't appear to be in the right place. It
may have been caused by a knock-on effect of another change. The
following seems to do the right thing, anyway. The change to the
position of the test is the fix to the problem you're noticing; the
change to the test itself is explained by the comment.
> 2. There are executable scripts in Functions/Misc, however 'make
> install' is installing them as non-executable files.
I don't think you're missing anything, we are. As the files are
functions, they don't *need* to be executable; presumably people have
been adding those that *can* be run stand-alone to the archive as
executable files, but no one's ever bothered to make the installer spot
this.
Index: Util/helpfiles
===================================================================
RCS file: /cvsroot/zsh/zsh/Util/helpfiles,v
retrieving revision 1.3
diff -u -r1.3 helpfiles
--- Util/helpfiles 30 May 2001 16:08:16 -0000 1.3
+++ Util/helpfiles 13 Mar 2006 18:50:33 -0000
@@ -107,7 +107,12 @@
undef($undented);
if (/^\s*$/ || ($undented = (/^(\s*)/ && length($1) < $indent))) {
$undented && &doprint($_);
- while (defined($_ = <>) && /(^\w)|(^\s*$)/) {
+ while (defined($_ = <>) && /(^\w)|(^\s*$)/) {
+ # NAME is the start of the next section when in zshall.
+ # (Historical note: we used to exit on the page header,
+ # but text from the old section can continue to the
+ # new page).
+ last BUILTINS if /^\s*NAME\s*$/;
last BUILTINS if /^STARTUP\/SHUTDOWN FILES/;
last if /^zsh.*\s\d$/; # GNU nroff -man end-of-page marker
}
@@ -121,11 +126,6 @@
} while (defined($_) && /^\s*$/);
}
}
- # In zshall, the zshcompctl manual page comes after the
- # builtins for 3.0, and zshzle comes after it for 3.1.
- if (/ZSH(COMPCTL|ZLE)\(1\).*ZSH(COMPCTL|ZLE)\(1\)/) {
- last BUILTINS;
- }
if (/^(\s*)/ && length($1) < $indent) {
# This may be just a bug on the SGI, or maybe something
# more sinister (don\'t laugh, this is nroff).
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
prev parent reply other threads:[~2006-03-13 18:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-13 18:15 Francisco Borges
2006-03-13 18:37 ` William Scott
2006-03-13 18:52 ` Peter Stephenson [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=EXCHANGE037oFJyi0Gf00015a38@exchange03.csr.com \
--to=pws@csr.com \
--cc=zsh-users@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).