I'm writing an #Emacs package. It's complete enough for a first release, but I should really include an Info file. I'm far more familiar with writing Org documents than TeXinfo documents, so I think I'll be writing the Info as an Org document, then exporting it as TeXinfo or Info.
@gabrilend @wyatt Are info pages any better? They're a hypertext system that Richard Stallman built for original Emacs in 1976, years before the Web.
I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs https://codeberg.org/rahguzar/filechooser , an Emacs interface to #hoogle https://codeberg.org/rahguzar/consult-hoogle
There is a (kind of in progress) major mode for #sagemath https://codeberg.org/rahguzar/sage-mode which hasn't seen much progress in a while because it is usable for its only user i.e. me.
Recently I managed to make produce a (humongous) #texinfo manual for Sage so that I can read it from Emacs https://github.com/sagemath/sage/issues/21734
@shegeley Hi,
I think it would be good to mark up the package description using Texinfo so that the list looks good not only in CLI but on the web too.
For an example:
https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/tex.scm#n10575
Which would translate to:
https://packages.guix.gnu.org/packages/texlive-crossword/
More info on Texinfo itemization:
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040itemize.html
And info about marking inline code:
https://www.gnu.org/software/texinfo/manual/texinfo/html_node/_0040code.html