tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Baptiste Daroussin <bapt@FreeBSD.org>
To: tech@mdocml.bsd.lv
Subject: support another man.conf(5) format or extending it
Date: Mon, 24 Nov 2014 13:50:19 +0100	[thread overview]
Message-ID: <20141124125019.GA11567@ivaldir.etoilebsd.net> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 639 bytes --]

Hi all,

While working on integrating mandoc(1) into FreeBSD I have not yet integrated
apropos and makewhatis because of the difference of format of man.conf(5).

Will you be against that I modifiy the man.conf(5) parser so that is does
support a minimum set of the FreeBSD's man.conf(5) ?
BAsically I'm think about mostly:

MANCONFIG
MANPATH

Here is the manpage of FreeBSD's version of man.conf(5)

Btw I think I'll try to make FreeBSD tracking the CVS version of mdocml rather
than the releases now because the CVS version works way better for me :)

Btw here is a small patch to fix build when HAVE_MANPATH is set.

Best regards,
Bapt

[-- Attachment #1.2: manpath-havemanpath.diff --]
[-- Type: text/x-diff, Size: 480 bytes --]

Index: manpath.c
===================================================================
RCS file: /cvs/mdocml/manpath.c,v
retrieving revision 1.18
diff -u -r1.18 manpath.c
--- manpath.c	18 Nov 2014 19:41:47 -0000	1.18
+++ manpath.c	24 Nov 2014 11:26:19 -0000
@@ -80,7 +80,7 @@
 	if ( ! ferror(stream) && feof(stream) &&
 			bsz && '\n' == buf[bsz - 1]) {
 		buf[bsz - 1] = '\0';
-		manpath_parseline(dirs, buf);
+		manpath_parseline(dirs, buf, 1);
 	}
 
 	free(buf);

[-- Attachment #2: Type: application/pgp-signature, Size: 181 bytes --]

             reply	other threads:[~2014-11-24 12:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 12:50 Baptiste Daroussin [this message]
2014-11-27  0:43 ` Ingo Schwarze

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=20141124125019.GA11567@ivaldir.etoilebsd.net \
    --to=bapt@freebsd.org \
    --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).