zsh-workers
 help / color / mirror / code / Atom feed
From: mason@primenet.com.au (Geoff Wing)
To: zsh-workers@sunsite.auc.dk
Subject: Re: PATCH: zsh-3.1.6-dev-17: Doc/Makefile.in rule: Zsh/modlist.yo
Date: 6 Feb 2000 23:38:27 GMT	[thread overview]
Message-ID: <slrn89s1fj.6dg.mason@coral.primenet.com.au> (raw)
In-Reply-To: <1000206194825.ZM12126@candle.brasslantern.com>

Bart Schaefer <schaefer@candle.brasslantern.com> typed:
:On Feb 6,  6:38am, Geoff Wing wrote:
:} Note also that I've removed the
:} CTRL-A's from the includefile() lines: any reason they were there?
:I think they were to work around a bug in some version of yodl or other.
:There should be some discussion in the archives about it.

OK, couldn't find anything about it but this puts them back in.
Follows my message 9584 &  Tanaka's 9585


--- Doc/Makefile.in.org	Mon Feb  7 10:34:29 2000
+++ Doc/Makefile.in	Mon Feb  7 10:35:06 2000
@@ -178,7 +178,7 @@
 		echo ")"; \
 	    done; \
 	    echo "enditem()"; \
-	    echo "includefile(Zsh/modmenu.yo)"; \
+	    echo "includefile(Zsh/modmenu.yo)\x01"; \
 	    set '' $(MODDOCSRC); \
 	    mod1= mod2= mod3=; \
 	    test ".$$2" = . || \
@@ -189,7 +189,7 @@
 		    mod3=`sed -n '1{s|^COMMENT(!MOD!||;p;q;}' < $(sdir)/$$3`; \
 		echo "texinode(The $$mod2 Module)($${mod3:+The $$mod3 Module})($${mod1:+The $$mod1 Module})(Zsh Modules)"; \
 		echo "sect(The $$mod2 Module)"; \
-		echo "includefile($${2})"; \
+		echo "includefile($${2})\x01"; \
 		shift; \
 		mod1=$$mod2; \
 		mod2=$$mod3; \
-- 
Geoff Wing : <gcw@pobox.com>     Work URL: http://www.primenet.com.au/
Rxvt Stuff : <gcw@rxvt.org>      Ego URL : http://pobox.com/~gcw/
Zsh Stuff  : <gcw@zsh.org>       Phone   : (Australia) 0413 431 874


  reply	other threads:[~2000-02-06 23:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-02-06  6:38 Geoff Wing
2000-02-06  8:03 ` Tanaka Akira
2000-02-06 19:48 ` Bart Schaefer
2000-02-06 23:38   ` Geoff Wing [this message]
2000-02-07  0:11     ` 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=slrn89s1fj.6dg.mason@coral.primenet.com.au \
    --to=mason@primenet.com.au \
    --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).