>>563
Use whatever you want, but more importantly make sure to put a bunch of typical usage examples at the top of every page. I always scroll straight to the examples in documentation and I'm sure I'm not the only one.
>>563
GNU info, so that it technically exists but basically nobody will ever find it and even if they do they'll give up before the interface takes its toll on their sanity.
>>563
GNU info, so that it technically exists but basically nobody will ever find it, and even if they do they'll give up before it takes its toll on their sanity, and even if they convert it to HTML the pages will be produced separately making it more difficult than necessary to navigate and search, and even if they convert it to a single HTML page it will be so long that aw fuck this this is why nobody writes good autotools scripts
>>573
I prematurely hit send on accident, not sure how, I do have phantom clicks and keystrokes on this turrible hardware. So now the world gets to laugh at my foolishness (but 'tis better, I find, to be laugh'd at than y-wept).
I am slightly serious about the autotools documentation, though, it's not like it's great and there are corner cases it won't help you with, but it probably tells what you want from an 80-20 perspective if only you could actually not have navigation issues in the way and if only it weren't a "do it this way or weird shit will happen" kind of suite.