From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from scc-mailout.scc.kit.edu (scc-mailout.scc.kit.edu [129.13.185.202]) by krisdoz.my.domain (8.14.3/8.14.3) with ESMTP id pAQCfA1B021078 for ; Sat, 26 Nov 2011 07:41:11 -0500 (EST) Received: from hekate.usta.de (asta-nat.asta.uni-karlsruhe.de [172.22.63.82]) by scc-mailout-02.scc.kit.edu with esmtp (Exim 4.72 #1) id 1RUHZ7-0005TZ-KB; Sat, 26 Nov 2011 13:41:09 +0100 Received: from donnerwolke.usta.de ([172.24.96.3]) by hekate.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RUHZ7-0001lB-JL for tech@mdocml.bsd.lv; Sat, 26 Nov 2011 13:41:09 +0100 Received: from iris.usta.de ([172.24.96.5] helo=usta.de) by donnerwolke.usta.de with esmtp (Exim 4.72) (envelope-from ) id 1RUHZ7-0005Lu-IC for tech@mdocml.bsd.lv; Sat, 26 Nov 2011 13:41:09 +0100 Received: from schwarze by usta.de with local (Exim 4.72) (envelope-from ) id 1RUHZ7-0005Mt-HU for tech@mdocml.bsd.lv; Sat, 26 Nov 2011 13:41:09 +0100 Date: Sat, 26 Nov 2011 13:41:09 +0100 From: Ingo Schwarze To: tech@mdocml.bsd.lv Subject: Re: mandocdb: handle formatted manuals Message-ID: <20111126124109.GE13912@iris.usta.de> References: <20111119005649.GA10365@iris.usta.de> <4ECE1B81.7080902@bsd.lv> <20111126115429.GB13912@iris.usta.de> <4ED0D535.6040408@bsd.lv> X-Mailinglist: mdocml-tech Reply-To: tech@mdocml.bsd.lv MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ED0D535.6040408@bsd.lv> User-Agent: Mutt/1.5.21 (2010-09-15) Hi Kristaps, Kristaps Dzonsons wrote on Sat, Nov 26, 2011 at 01:01:57PM +0100: > Ingo Schwarze wrote: >> Currently, we have >> >> recno -> filename \0 section \0 title \0 arch \0 description \0 >> >> Given that the description will typically be dozens of characters, >> i don't think encoding the file type in a single byte with a set >> of #defines is worth the obfuscation, so i'd just make that >> >> recno -> type \0 filename \0 section \0 title \0 arch \0 description \0 >> >> where type = ( mdoc | man | cat ). > That's exactly what I had in mind. I think it's pretty clear which > areas will need the offset calculation. mandocdb(8) will also need > to be updated -- come to think of it, it already needs updating with > the new types. Do you want to do that, or shall I? Feel free to, and/or use all or part of the suggestions i just sent in a parallel mail (that draft was rotting here for a week, now i sent it). >> I don't think any other information is required in the index. >> >> However, you planned to check endian-neutrality, right? > Yes, although this is purely a mechanical check (it is absolutely > necessary). I'll do this when your above changes have been checked > in so we avoid clobbering each other. > > Til then, I'll work almost exclusively with man.cgi and manup. By > the way, any suggestions for manup's name? Just "man up" and tell > me. ;) To avoid the NIH syndrom, this is what i find on one a Linux system i have access to: NAME catman - create or update the pre-formatted manual pages SYNOPSIS catman [-dhV] [-M path] [-C file] [section] ... I think we should not implement the -d, -h, and -V options, but the -M argument is great. On OpenBSD, we would use man.conf(5) by default, and elsewhere, maybe manpath(1) - i haven't really looked into the latter yet, but clearly don't like it, it's even worse than man.conf(5) with respect to overengineering, but probably there is nothing for us to decide. Maybe we don't need the section arguments either, just use the sections found on disk. If we ever get bored, we can add -C to mandocdb(8), apropos(1), and catman(8). In summary, the tool is going to be similar enough that we don't need to invent a new name. That's not to say that i consider the name catman(8) to be well-chosen, but at least it's an established name for the thing. Or what do you think? Yours, Ingo -- To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv