NOWEB(7)

✨ NOWEB(7) ✨

okay bestie so real talk — this one's the manual page for nowebfilters, which is literally filters and parsers for use with noweb. the manual name is NOWEB(7), in case you were wondering, and yes it's a Miscellaneous Information Manual situation 💅

---

🌸 SYNOPSIS 🌸

[noweave|notangle|noweb] [-filter filter|-markup parser] ...

---

💖 DESCRIPTION 💖

so this page is the lil directory of all the filters and parsers that ship with noweb(1). here's the vibe:

• a filter transforms the pipeline representation, and you use it with the -filter option.
• a parser reads a source file and emits the pipeline representation, and you use it with the -markup option.

and no cap: not all filters and parsers are available at all installations. it's giving "depends on your setup", fr fr 🙈

---

🎀 FILTERS 🎀

• autodefs.* — noweave's -autodefs and -showautodefs options use these filters, and they automatically find defined identifiers. the * stands for the name of a programming language. (Icon installation only.)
• btdefn — the btdefn filter uses Dave Hanson's convention to mark definitions. in code chunks, each defining instance of an identifier should be preceded by a single backtick character (ASCII 140). the btdefn filter removes these backticks from the code and converts them to definitions, thus: definition. it, not @ %def, should be used with both notangle(1) and noweave(1), at least for programs written in C-like languages. slay.
• disambiguate — the disambiguate filter makes it possible to abbreviate chunk names using a trailing ellipsis (three periods), in the style of WEB and nuweb(1). iconic honestly.
• docs2comments options — the docs2comments filter converts documentation chunks to comments in code chunks. options include:
  • -all, which converts all documentation chunks into comments
  • -one converts only one documentation chunk preceding each code chunk
  • -wk formats comments k columns wide.

other options control the language and style of the comment. languages available include -awk, -c, -c++, -f77, -f90, -icn, -icon, -lisp, -m3, -ml, -ocamlweb, -pascal, -scm, and -tex.

Norman recommends using notangle(1) with docstocomments instead of nountangle(1). (Icon installation only.)

• elide patterns — the elide filter removes from the stream any code chunk matching any of the arguments. each argument is a pattern in which ? matches any single character and * matches any sequence of characters. bye girl 👋
• emptydefn — the emptydefn filter makes an empty definition (<<>>=) an abbreviation for a continuation of the previous definition. lowkey genius.
• l2h [-show-unknowns] [-html-quotes] — the l2h filter converts LaTeX to HTML in documentation chunks. if the -show-unknowns options is given, unrecognized LaTeX control sequences appear in bold in the output. if the -html-quotes option is given, l2h converts LaTeX double-quote ligatures into HTML 4 double-quote entities. l2h uses the LaTeX-generated .toc and .bbl files to help create table of contents and bibliography. (Icon installation only.)
• pipedocs command — the pipedocs filter runs each documentation chunk through an invocation of command, which may be any Unix command. the Noweb library includes the command h2a, which uses lynx(1) to convert HTML to ASCII.
• xchunks files — the xchunks filter pulls in code chunks from an external source. the files argument lists one or more noweb files, which are used only for their definitions of code chunks. empty chunk definitions in the main document are replaced with the external definitions of the same name. this filter makes it possible to include the same code chunks in multiple documents, or even the same code chunks multiple times in the same document. (Icon installation only.)

---

🦋 PARSERS 🦋

a parser converts a source file to the noweb pipeline format, interpreting the ``markup'' in that file. by default, the tools use the standard noweb markup, but some installations may support nuweb markup as well. parsers include:

• markup — converts standard noweb(1) markup to pipeline format.
• numarkup — converts nuweb(1) markup to noweb pipeline format. it is not part of the standard installation, but it can be found in noweb's contrib/norman directory.

---

🍓 FILES 🍓

all filters and parsers are stored in /usr/lib/noweb

---

💀 BUGS 💀

it is possible to tell l2h about new control sequences by putting special TeX comments in one's documentation chunks, but there's no documentation. use the source, Luke. 😭

numarkup loses information, e.g., about the proper treatment of tabs. it also doesn't compensate for notangle's newline-removal heuristic, which means results on nuweb files may differ subtly from those produced by nuweb.

many filters are not available in installations that use Awk instead of Icon. so if your fave filter is missing... that might be why bestie 🫶

---

🌈 SEE ALSO 🌈

• noweave(1), notangle(1), noweb(1)
• The Noweb Hacker's Guide

---

👑 VERSION 👑

this man page is from noweb version 2.12.

---

💜 AUTHOR 💜

Norman Ramsey, Tufts University. Internet address Norman.Ramsey@tufts.edu. Noweb home page at http://www.cs.tufts.edu/~nr/noweb.

---

and that's the whole page, bestie ✨ this one came from the local crew dated 10/40/2008 — yes the date says 10/40, no I will not be explaining that, it's giving typo icon 💅 mwah, go write some literate programs 💖