>>>>> Colin Watson <[EMAIL PROTECTED]> writes:

[...]

 >> It was suggested that man-db gets one more command as well, to
 >> do the checking in a ``standard way''.  So, I suggest the
 >> following:

 >> * add support for an MANROFFOPT environment variable to specify
 >> extra arguments to groff (analogous to MANROFFSEQ and MANOPT);

 > I like this, thanks; I've applied your patch with a few small
 > modifications, and also added documentation of it to man(1).

        Thanks!

 > If you want to check this out, install bzr and run:

 > bzr get http://www.chiark.greenend.org.uk/~cjwatson/bzr/man-db/trunk/

        I'm glad to see that so many projects benefit from using DVCS'
        nowadays!  (Though I've recently had some problems managing a
        Mercurial repository -- there're just so many DVCS'...  Anyway,
        1.5 years experience with GNU Arch helps much.)

        Unfortunately, there're a plenty of projects I'm interested to
        participate in which still use centralized VCS'...

 >> * add a command, `manwe' (for ``MAN with Warnings Enabled''),
 >> which will behave just like `man', but with (some) Groff
 >> warnings enabled;

 > While I appreciate the Silmarillion pun :-),

        Well, I was just struck by the fact that `manwe' could be an
        appropriate name for such a program.  Indeed, it's even more
        appropriate than `manlint', which was suggested before (since
        `lint' is a static analysis tool, and `groff -wmac' certainly
        isn't.)

        I just had no chance to resist writing a patch!

 > I'm not very keen on another command just for this. I would rather
 > have something like 'man --warnings'.

        May I suggest --warnings[=WHICH-ONES] then?

 > Once I finish converting man to argp, it will be easier to add
 > options without trashing translations every time.

        In general, I don't care that much about the way this behaviour
        is triggered.  However, I'd really be happy if Bug#377392 would
        be closed soon.

        Certainly, Argp allows argument parsing to be implemented in a
        much flexible way.

 >> Please note that `manwe' would only work as intended if `man' is
 >> to call `groff'.  So, `-t' option may be necessary, e. g.:

 >> $ manwe -t ifconfig > /dev/null 
 >> <standard input>:63: warning: `Note:' not defined
 >> $ 

 > I just sent a patch to the groff mailing list to teach its nroff shell
 > script about -w and -W options. If this is accepted upstream, I'll also
 > apply it to the Debian groff package.

        ACK.

 >> --- man-db-2.5.0-debian-3/src/man.c 2007-11-24 01:54:12.000000000 +0600
 >> +++ man-db-2.5.0-debian-3-manwe/src/man.c   2007-11-24 02:15:52.000000000 
 >> +0600
 >> @@ -1522,6 +1529,7 @@
 >>             cmd = command_new_args (fmt_prog, file, pp_string, NULL);
 >>             if (roff_device)
 >>                     command_arg (cmd, roff_device);
 >> +           command_argstr (cmd, roff_opt);
 >>             pipeline_command (p, cmd);
 >>     }
 >>  

 > Note that this part is incorrect because, for better or worse, the
 > interface to custom format programs doesn't support adding *roff options
 > (see e.g. tools/mandb_fmt-script). Fortunately, as far as I know hardly
 > anyone uses this feature.

        I must confess that I don't really understand this ``external
        formatter'' feature.  May it be useful to specify extra options
        to one?  Should it be done differently (e. g., via a different
        environment variable)?




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to