tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: Re: mandocdb: handle formatted manuals
Date: Sat, 26 Nov 2011 13:41:09 +0100	[thread overview]
Message-ID: <20111126124109.GE13912@iris.usta.de> (raw)
In-Reply-To: <4ED0D535.6040408@bsd.lv>

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

      reply	other threads:[~2011-11-26 12:41 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-19  0:56 Ingo Schwarze
2011-11-24 10:25 ` Kristaps Dzonsons
2011-11-26 11:54   ` Ingo Schwarze
2011-11-26 12:01     ` Kristaps Dzonsons
2011-11-26 12:41       ` Ingo Schwarze [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=20111126124109.GE13912@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /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.
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).