From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.dk
Subject: PATCH: An alternative nroff fix to 12724
Date: Thu, 31 May 2001 04:57:56 +0000 [thread overview]
Message-ID: <1010531045756.ZM5405@candle.brasslantern.com> (raw)
Add a single space in a strategic spot, and you prevent yodl from running
the PARAGRAPH() macro, which is where all the mess comes in.
The real root of the problem is that the macro definitions in yodl can't
be pushed on a stack, so zman.yo settles for toggling them between two
states. Of course, when you have a startitem() nested inside another
startitem(), two states is not enough.
--- zsh-forge/current/Doc/Zsh/builtins.yo Wed May 30 21:47:06 2001
+++ zsh-4.0/Doc/Zsh/builtins.yo Wed May 30 21:47:20 2001
@@ -831,7 +831,7 @@
with tt(-c) or tt(-l), with tt(-q) which clears the input queue before
reading, or within zle where other mechanisms should be used to test for
input.
-
+ifzman( )
Note that read does not attempt to alter the input processing mode. The
default mode is canonical input, in which an entire line is read at a time,
so usually `tt(read -t)' will not read anything until an entire line has
@@ -840,8 +840,7 @@
character is tested, so that e.g. `tt(read -t -k 2)' can still block on the
second character.
)
-ifnzman(enditem()
-)
+enditem()
If the first argument contains a `tt(?)', the remainder of this
word is used as a var(prompt) on standard error when the shell
is interactive.
@@ -857,7 +856,6 @@
cancels both tt(-p) and tt(-u).
The tt(-c) or tt(-l) flags cancel any and all of tt(-kpquz).
-ifzman(enditem())
)
cindex(parameters, marking readonly)
alias(readonly)(typeset -r)
--
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 reply other threads:[~2001-05-31 4:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-31 4:57 Bart Schaefer [this message]
2001-06-01 14:00 ` Peter Stephenson
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=1010531045756.ZM5405@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--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).