Results 1 ... 22 found in all logged channels for 'texinfo'
(pest) phf[busybot]: which also means that i use texinfo to produce technical documents, but looking at your hevea output i'm a bit jelous, because i know texinfo won't give me something that pretty out of the box
(asciilifeform) dulapbot: Logged on 2021-12-28 14:25:57 asciilifeform: considering switching pest spec from 'markdown' (which makes renumbering endnotes a 1st class bitch) to ~anyffin~ else, even e.g. the loathesome 'texinfo' if no one suggests a workable alternative
(asciilifeform) asciilifeform: 'texinfo' (plentiful gripes in logs, it's a bitch to build) knows how to output html
(asciilifeform) thimbronion: asciilifeform: Never found a solution to numbering in markdown. I know nothing about texinfo/latex.
(asciilifeform) asciilifeform considering switching pest spec from 'markdown' (which makes renumbering endnotes a 1st class bitch) to ~anyffin~ else, even e.g. the loathesome 'texinfo' if no one suggests a workable alternative
(asciilifeform) asciilifeform rather fond of tex on acct of being a dead-tree aficionado, and used many times for internal 'proggy to paper to hammock' process . but never once used texinfo
(asciilifeform) signpost expects no one to use texinfo for anything himself other than ^
(asciilifeform) signpost: http://logs.nosuchlabs.com/log/asciilifeform/2021-09-01#1055890 << since found, and turned out to be more scripts that weren't getting chmod +x in texinfo's build script.
(asciilifeform) cgra: texinfo generates it's manpages using help2man, and help2man generates its info pages using texinfo
(asciilifeform) cgra: the stage 2 didn't work for me as is, because texinfo seems to depend on help2man, *and* vice versa
(asciilifeform) trinque: both ./install and ./install-set take a -j$NUMJOBS param, but I'd be careful about using that on the first build. I encountered a bug in texinfo just now using -j12
(asciilifeform) asciilifeform: afaik 'texinfo' is simply dross, does 0 useful
(asciilifeform) shinohai: Ironically I didn't have to carve out texinfo from gpg until I switched to musl.
(asciilifeform) asciilifeform: trinque: iirc i had to manually cut the texinfo crapolade from at least gpg 1.4 before it'd build
(asciilifeform) trinque: shinohai: if you mean building texinfo itself; appears to be gagging on a translation-related file, which is curious given I'm configuring like this -> ./configure --disable-nls --prefix=$PREFIX LINGUAS="en"
(asciilifeform) shinohai: I had texinfo cause a headache when building that static gpg-1.4.10, will dig up the build notes in a bit if helpful.
(asciilifeform) trinque: src is known to be clean on every build; I copy src to /tmp/build/texinfo.XXXXXX to build
(asciilifeform) trinque: anyone have any experience building texinfo? the motherfucker randomly fails only some builds.
(asciilifeform) trinque: all of this can be cleaved off, but needs to be actually cleaved off. there are bugs in the gcc build process where it claims you can get away without autoconf/automake/texinfo, but that is unreliable.
(asciilifeform) trinque: also texinfo, also fuck my eyes.
(trilema) phf: fwiw dpans has a copy of tex source, first or second to last draft before the standard was sent over to ansi. there's two projects that cleanup that tex, one is dpans2texi which produces texinfo formatted (this is what i use from emacs) and another by some russians that produces a clean pdf with hyperlinks