| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
| |
value part of the index. This is the actual manual section---before,
mandoc.cgi was relying on the file suffix, but this can be (e.g.) .man or
whatnot. This is The Correct Way (tm).
|
| |
|
|
|
|
| |
manuals. This covers the majority case.
|
|
|
|
| |
segfault in NetBSD.
|
|
|
|
| |
documents.
|
|
|
|
| |
those that are quoted and not angular-bracketed).
|
|
|
|
|
| |
the generated index and keyword databases). Add some documentation
within mandoc-db.c.
|
|
|
|
| |
keyword database, which references the index of hard-coding files.
|
|
|
|
|
|
| |
database from a directory, instead of a path. This is because it'll
also output an index of files to that same directory. Add documentation
to the local variable names, too.
|
|
This will be used during BSDCan-2011, paired with a web front-end, as a
demonstrandum of semantic annotations (mdoc) versus those of man. This
isn't linked to the build in any way but for cleaning created files. This
code has been heavily tested under valgrind and is known to work on
GNU/Linux (needs -ldb library), all BSDs, and Mac OSX.
Please don't repost this, for the time being, as I don't want to spoil the
fun for the conference. This utility is still constantly under development
(e.g., it will also generate a recno database of filenames and `Nd' output
so that paths needn't be hard-coded) but is mature enough to warrant being
checked in.
|