On Sat, Sep 06, 2008 at 12:37:49PM +0000, hyjial wrote:
> Hi,
> After having spend some time reading man (1) code, the following
> proposal comes :
i think you will find you have a better chance of things getting
accepted if you submit a diff.
if you can;t code, like me, there's not much point submitting
descriptions of how to do stuff. probably lots of developers could do
this, if they wanted, and had the time, motivation, etc.
marc espie told me the escape sequence stuff comes from linux (or gnu,
or whatever), so you could start by looking there to see how it's done.
jmc
> Create a keyword for man.conf (5) - _ibuild for example - for lines
> like : ``_ibuild - a letter - - associated command -''
> The letter would appear on the first line of the manpage file and
> would be separated from the leading ``{.,'}\"'' by white spaces and single.
> man (1) would accept both (in fact, it would go to the first blank character
> and start from there). This would be triggered only in case of a
> .[1-9n]{,[a-z]}{,.{gz,Z}} extension. man (1) would insert the command
> given by the ``_ibuild'' line right before the `` {,|} /usr/bin/nroff -man'',
> removing the trailing ``%s'' as needed.
> Triggering the in-file inquiry would be more easily implemented as
> a config file setting - a ``_iext (extension list)'' line -
> As an additionnal possibility, why not allow skipping in-file inquiry
> for some directories - those in ``base'' mostly - using an ``_iskip''
> keyword in man.conf (5).
> Suggestions ?
> Personnaly I find it a bit intrusive for man.conf (5).
> Cheers.
