From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8836 invoked from network); 2 Jun 1999 07:54:36 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 2 Jun 1999 07:54:36 -0000 Received: (qmail 6771 invoked by alias); 2 Jun 1999 07:54:13 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6432 Received: (qmail 6743 invoked from network); 2 Jun 1999 07:54:00 -0000 Message-Id: <9906020726.AA16770@ibmth.df.unipi.it> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: PATCH: pws-20: info formatting In-Reply-To: ""Bart Schaefer""'s message of "Tue, 01 Jun 1999 18:50:45 DFT." <990601185045.ZM11271@candle.brasslantern.com> Date: Wed, 02 Jun 1999 09:26:21 +0200 From: Peter Stephenson "Bart Schaefer" wrote: > On Jun 1, 5:03pm, Peter Stephenson wrote: > } Subject: PATCH: pws-20: info formatting > } > } In an aside in a message which hasn't got back to me yet, I queried the > } excess use of quoting in zsh.info*: it's not too surprising you get this > } sort of clash in a documentation system written in half a dozen > } incompatible languages at once. > > See zsh-workers/4053 and associated thread for more on this, particularly > Zefram's remarks on the matter. > > Personally, I prefer the appearance after Peter's patch, but ... Actually, I think my patch is consistent with Zefram's remarks. He's saying tt() is for the font, `...' is for quotation --- that's exactly how it is after my change. Before, tt() was *also* introducing quotes (but only in info, so perhaps it didn't get noticed); after, the quotes are just the way we put them. However, I've been negligent about putting quotes around some of my stuff, including rewrites for parameter expansion, so I'll have a look at this again now it's more obvious in info. I never bothered reading Util/zsh-development-guide until now. > (Aside: Are there some LPAR() and RPAR() needed in the new text from > 6416? And correspondingly different placements of tt()? I'm never > sure what ought to be happening with LPAR() and RPAR().) Thinks like `tt((f))' work OK as long as the parentheses are balanced. If you have unbalanced parentheses you have to resort to e.g. `tt(LPAR())var(flags)tt(RPAR())'. -- Peter Stephenson Tel: +39 050 844536 WWW: http://www.ifh.de/~pws/ Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy