tedoc.tes(1)

πŸ“¦ version 2.5.2, in alpine 3.24

tedoc.tes(1) β€” hiii bestie, welcome to the General Commands Manual, this one's the page for tedoc.tes and it is genuinely so useful, trust πŸ’…

🌸 NAME 🌸

tedoc β€” the source code documentation tool for SciTECO. that's the whole vibe, no cap.

✨ SYNOPSIS ✨

tedoc.tes [-C] [--] output template sources...

πŸ¦‹ DESCRIPTION πŸ¦‹

okay so tedoc is a tool for extracting documentation from SciTECO macros and from C/C++ code, which is honestly iconic of it. it's used to document SciTECO's internal commands as well as macro packages ✨

the way it works: it processes special SciTECO comment blocks out of the sources, generates troff man-page markup, and inserts that markup into a man-page template right at the position of the TEDOC pseudo-request πŸŽ€ then the result gets written to an output file. so lowkey tedoc can be understood as a troff preprocessor β€” that's the whole personality 🫢

πŸ’– OPTIONS πŸ’–

  • -C β€” instructs tedoc to extract C/C++ comments instead of SciTECO comments. the C comments begin with /*$ and end with */. the SciTECO comments, in contrast, begin with !*$ and end with *! πŸ’€ (yes, different delimiters, keep up bestie)
  • output β€” the resulting man-page file πŸ“„
  • template β€” a man-page template, i.e. a man-page with the TEDOC request in it πŸŽ€
  • sources... β€” an arbitrary number of source code files to scan through. ngl, the comments are extracted in document order, i.e. from the first comment in the first source file to the last comment in the last source file specified πŸ‘‘

🧚 TEDOC COMMENTS 🧚

the tedoc source code comments support a small but powerful semantic markup for documenting SciTECO commands and macros, and it's giving main character energy:

  • comments start with !*$ (or /*$ in C/C++ mode) ⭐
  • the first line (immediately after the starting comment) may contain topic keywords for SciTECO's online help system that will point to the beginning of the section generated for this tedoc comment. this generates SCITECO_TOPIC macro calls defined in sciteco.tmac (see grosciteco.tes(1)). πŸ”₯
  • all lines until first empty line are syntax descriptions ✍️
  • text followed by -- is a short description 🩷
  • variable values and characters of syntactic significance should be detected automatically πŸ€–
  • alternatives are denoted by | β€” pick a lane, or don't πŸ’…
  • every line is an alternative (e.g. different calling forms of the same command or macro) 🌈
  • return values may be specified after -> 🎯
  • the remaining text is the verbose command description πŸ“š
    • <name> denotes a variable from the syntax description 🏷️
    • empty lines introduce paragraphs πŸ“
    • lines beginning with - are unordered lists πŸ“
    • lines beginning with numbers and dot (1., 2., etc.) are ordered lists πŸ”’
    • these transformations are only preprocessing, so that troff requests, macros and escapes may also be used freely 😭 (yes, freely, go off)

πŸŽ€ SEE ALSO πŸŽ€

  • SciTECO invocation and help on its environment variables: sciteco(1)
  • a GNU roff post-processor for rendering troff markup into β€œwomanpages” for SciTECO's online help system β€” also documents special troff macros in sciteco.tmac: grosciteco.tes(1) πŸ’œ
  • the GNU roff β€œman” macros for writing man pages: groff_man(7) πŸ‘‘

πŸ‘‘ AUTHOR πŸ‘‘

this manpage and the SciTECO program was written by Robin Haberkorn. absolute legend fr fr πŸ™Œ


and that's the page!! πŸ¦‹ this was SciTECO Version 2.5.2, dated 30 Apr 2026 β€” slay, go document something, ily bye πŸ’–βœ¨

πŸ“¦ where this page comes from