>>>>> Colin Watson <[EMAIL PROTECTED]> writes: [...]
>>> 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! [...] > I think my scars from using GNU Arch are finally fading. If you > haven't used bzr before, you should find it to have most of the > benefits and few of the drawbacks; its designers were certainly very > aware of both aspects of Arch. One advantage of GNU Arch is that it allows one to make local branches for remote projects without having to clone the whole remote repository. AFAIK, it's the feature that most of the DVCS are still lacking. (GNU Arch is also the only DVCS with repository format that I understand quite well. Although it's not an advantage to anyone but me.) >> Unfortunately, there're a plenty of projects I'm interested to >> participate in which still use centralized VCS'... > I have an ulterior motive, of course; I could do with more people > than just me working on man-db. :-) If it becomes necessary, I'll be > happy to move up my list the task of moving man-db's bzr repository > to somewhere where I can give access to other people, but in the > meantime I expect that just making branches will work fine. My opinion is that making branches is fine, as long as there's someone to collect the changes and to integrate them into a central repository (of some sort.) >>> I'm not very keen on another command just for this. I would rather >>> have something like 'man --warnings'. [...] > Feel free to try it on top of my argp branch, in fact: > http://www.chiark.greenend.org.uk/~cjwatson/bzr/man-db/argp/ I'll check it. > I'm not sure what to do about the IX thing; an option called --warnings > doesn't really seem to reflect the possibility of prepending some groff > input which does some other stuff. Yet, I think the important thing here > is that it should be easy for people to check their manual pages, and > that the option we add should reflect that. > How about an option called --audit (and perhaps something like > --audit-warnings=mac,escape if you want finer control)? Why not --audit and --warnings[=...]? The former given without the latter will behave as if the latter is given without an optional argument, while the latter given without the former will just switch Groff warnings on, while not adding the `-maudit'. > When used, it would add something like -wmac -M/usr/share/man-db > -maudit to groff's command line options. /usr/share/man-db/audit.tmac > would be a bit like what you suggested for man.local and mdoc.local > in #377392, except that [... it's completely different?...] > so it would just need to be: > .\" Work around pod2man bug: IX is only defined if the F register is > .\" non-zero. > .de IX > .. > ... and whatever other workarounds are necessary. Sounds good. [...] >> 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)? > I recommend ignoring external formatters. As far as I'm concerned > they're an obsolescent feature retained purely for compatibility. [...] ACK. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
