techhub.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
A hub primarily for passionate technologists, but everyone is welcome

Administered by:

Server stats:

4.6K
active users

#groff

0 posts0 participants0 posts today
Replied in thread

@stafwag

The Hell of it is that grotty actually supports coloured manual pages natively, and has done all along, since the 1990s. Its own manual page is actually in colour.

Debian and others have actually patched hidden flags in to turn grotty's colour and font capabilities off, about a quarter of a century ago, and they're still there.

Simply getting rid of those patched flags makes quite a difference.

jdebp.uk/Softwares/nosh/italic

jdebp.ukItalics and colour in manual pages on a nosh user-space virtual terminal
Replied in thread

@jabref Et dans ma veille, il y a bien sûr un article récent sur #refer et son #format avec #Groff :
%0 Article
%T Making references in groff
%A Jim Hall
%D 2025-05-06
%U technicallywewrite.com/2025/05
%X Intérêt pour l'importation : plusieurs A possibles sur 1 ligne. Autre intérêt : détails sur le formatage des références. Jim Hall est un expert Unixien, auteur notamment de de FreeDOS et il a publié sur ce site d'autres articles sur groff.
Bonne lecture et bonne utilisation !

technicallywewrite.comTechnically We Write

I guess I’m doing something of a competition between #Emacs #orgmode export to #LaTeX and lovingly hand-crafted #heirloom #doctools #troff (-me).
I briefly considered an export from #orgmode to #groff (-ms) via #pandoc to see if the two approaches could possibly share anything, but that may be a gulf that is not worth crossing.

One of the macros I had coded up was to present something as a link to its entry in the appendix the first time it appeared on a new page, and ordinary text without link for subsequent mentions on the same page. While I’m sure there is a way to do this in the #TeX universe, I don’t know (yet) if it is considered sufficiently within the #LaTeX mindset to be worth attempting.

Building up from physical to logical to semantic markup feels more natural in #troff. Reaching down from #LaTeX into #TeX to perform computation in your document feels discouraged, doubly so when exporting from #orgmode. It is a wonderful method for planning, organizing, and ultimately creating a beautiful document from a single source file.

Different people want different things out of their typesetting systems. I’m glad to have spent some time in both the #troff and #TeX worlds.

Don’t get me wrong; I’m reasonably proud of what I have accomplished with #heirloom #doctools (a.k.a. #troff that is not #groff) and I even learned a few neat #makefile tricks along the way. But given how much time I spend with #emacs and #orgmode perhaps I should seriously investigate duplicating or imitating the work in #LaTeX. It did not take as long as I feared it would to get the color and font matters worked out. The #macros look like they will translate easily enough, with some support from #elisp. Links and bookmarks look like they will work themselves out. Pictures could be…interesting.

Replied to www-gem

@wwwgem nroff user, mostly, not GNU gnroff.

I prefer nroff with -mdoc when the primary end result does not need pictures or where plaintext availability has high value (e.g. manpages, but also other systems documentation). This is very nice to write, much nicer than Tₑχ/LᴬTᴇΧ or -man, and semantic markup.

Then GNU groff can be used to provide an additional PDF which is at least somewhat legible, and I do my own HTML conversation from the plaintext output, but mdocml (now called mandoc) can be used to create somewhat good HTML if you stick to -mdoc commands instead of using nroff primitives. (Which I tend to not do.)

I very much dislike how the GNU g{,n}roff macropackages have changed with the last release. The MirBSD nroff macropackages, specifically -mdoc, work well with GNU g{,n}roff and mostly avoid the pain. (Writing \- and a font hack were still needed.)

nroff with -man is just ugly and awful, stay away from it.

nroff with -ms (+), -me (ref), etc. is also possible, but I found -mdoc more modern and therefore less buggy.

I haven’t yet used neqn (doc, guide) or pic and only a little tbl (doc) (mostly, the native -mdoc tables suffice); AT&T nroff does not have a working pic and it doesn’t transfer to plaintext output well anyway.

I use Tₑχ/LᴬTᴇΧ when the end result primarily must be a PDF with pretty pictures (such as the installation manual of a software at $dayjob we handed to paying customers) or for more programmability. Though copy/paste from those PDFs is so bonkers I patched lstlisting to also dump the listings to a .lst file we provide along, so the admin can copy/paste the commands, examples and config files from there.

(I’ve never used $…$ math mode. I’m not in academics ☻)

I’ve pimped both (have my own Tₑχ/LᴬTᴇΧ styles/class and packages, and tweaked my groff fonts (example) and bugfixed the raw roff that implements the macros). I use both depending on where.

For my Mu͒seScore workshop, I even have a link list (source) written in a roff-like format that I convert to both Tₑχ/LᴬTᴇΧ (for PDF output) and HTML (for the website) using a Korn shell script, so much I like the format and structure.

Otherwise I’m somewhat a fan of plaintext (with UTF-8 line drawing, etc.) but not rST or md, and a large fan of just handwriting XHTML/1.1 snippets that can be included in webpages. (This ofc doesn’t transfer well to PDF.)

mbsd.evolvis.orgRTFM nroff(1)
#nroff#groff#tex