4 ms·
Getting used to browsing info pages in Emacs is something that is rather nice. You can do similar with man pages, there. Often times, it will let you jump dir
by taeric 2y ago
Getting used to browsing info pages in Emacs is something that is rather nice. You can do similar with man pages, there. Often times, it will let you jump directly to the source code of includes and such, if you want to take a peak at the actual code.
To that end, I fully agree with the idea. The richness of existing man pages is far nicer than many people seem to realize.
I do find a bit of dismay at the folks that want to ditch some of that richness and move to markdown or similar. That lets you layout some things fine, I think. I am 100% convinced that as you try to get all of the linking and general semantics of the existing solution done, you will find that you have added a lot of "schema" expectations to markdown that isn't there by default. And then you will start to build "markdown schema" tools to check that what you have fits some standards. And then...
Seriously, just look at a lot of the data that moved to JSON from XML. I saw they are trying to add namespaces to JSON in some projects. Truly terrifying to see people slowly and poorly add the features of the more complicated thing they avoided the first time around.
- m463 2y agoI think markdown is actually too heavy. It is really a layer over HTML, which seems to mean you have to have a browser.
- taeric 2y agoI think the larger problem with markdown is that it is not semantic at all? Yes, the "break glass to drop into html" is a problem. I'm assuming folks would try to disallow inline html, though?
- arcfour 2y agoIt's honestly hilarious to watch people poorly hack everything XML had back on top of JSON, but this time without any sort of standard.
- taeric 2y agoHilarious, but largely in a scary and sad way.