home.social

#texinfo — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #texinfo, aggregated by home.social.

  1. Käyttääköhän kekään enää #Texinfo'a? Siis ainakaan alkuperäiseen tarkoitukseensa #man-sivuja laajempana järjestelmän ohjeistuksena? Enää #Debian'kaan ei tunnu asentavan infoa oletuksena, vaikka nimenomaan #GNU'n ohjelmissa joskus man-sivu on tynkä ja varsinainen tieto info-sivulla. #floss #linux #unix #manpages #infopages

  2. Käyttääköhän kekään enää #Texinfo'a? Siis ainakaan alkuperäiseen tarkoitukseensa #man-sivuja laajempana järjestelmän ohjeistuksena? Enää #Debian'kaan ei tunnu asentavan infoa oletuksena, vaikka nimenomaan #GNU'n ohjelmissa joskus man-sivu on tynkä ja varsinainen tieto info-sivulla. #floss #linux #unix #manpages #infopages

  3. Käyttääköhän kekään enää #Texinfo'a? Siis ainakaan alkuperäiseen tarkoitukseensa #man-sivuja laajempana järjestelmän ohjeistuksena? Enää #Debian'kaan ei tunnu asentavan infoa oletuksena, vaikka nimenomaan #GNU'n ohjelmissa joskus man-sivu on tynkä ja varsinainen tieto info-sivulla. #floss #linux #unix #manpages #infopages

  4. Käyttääköhän kekään enää #Texinfo'a? Siis ainakaan alkuperäiseen tarkoitukseensa #man-sivuja laajempana järjestelmän ohjeistuksena? Enää #Debian'kaan ei tunnu asentavan infoa oletuksena, vaikka nimenomaan #GNU'n ohjelmissa joskus man-sivu on tynkä ja varsinainen tieto info-sivulla. #floss #linux #unix #manpages #infopages

  5. Käyttääköhän kekään enää #Texinfo'a? Siis ainakaan alkuperäiseen tarkoitukseensa #man-sivuja laajempana järjestelmän ohjeistuksena? Enää #Debian'kaan ei tunnu asentavan infoa oletuksena, vaikka nimenomaan #GNU'n ohjelmissa joskus man-sivu on tynkä ja varsinainen tieto info-sivulla. #floss #linux #unix #manpages #infopages

  6. 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.

    #TeXinfo #emacs #org #orgmode

  7. I'm writing an 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.

  8. 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.

    #TeXinfo #emacs #org #orgmode

  9. 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.

    #TeXinfo #emacs #org #orgmode

  10. 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.

    #TeXinfo #emacs #org #orgmode

  11. My stupid clipboard-speaker is at version 1.1.1.

    https://codeberg.org/kakafarm/guile-clipboard-speaker/commits/tag/v1.1.1

    The Guix package compilation phase of the `README.org` into a
    /usr/share/info/clipboard-speaker.info.gz in the guix.scm file was
    stolen from Protesilaos's emacs-denote guix package definition. The
    org-mode headers from emacs-denote's org-mode documentation file.

    #accessibility
    #clipboard
    #guile
    #guix
    #texinfo
    #texttospeech
    #tts
  12. @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.

    #Texinfo #infopages

  13. @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.

    #Texinfo #infopages

  14. @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.

    #Texinfo #infopages

  15. @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.

    #Texinfo #infopages

  16. @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.

    #Texinfo #infopages

  17. Managed to built in #saltstack manual as #TexInfo Info manual. Just 4.7 MB Gzip compressed. It takes some time to load but it's better than the previous man 7 salt thou.

  18. Managed to built in #saltstack manual as #TexInfo Info manual. Just 4.7 MB Gzip compressed. It takes some time to load but it's better than the previous man 7 salt thou.

  19. Managed to built in #saltstack manual as #TexInfo Info manual. Just 4.7 MB Gzip compressed. It takes some time to load but it's better than the previous man 7 salt thou.

  20. Managed to built in #saltstack manual as #TexInfo Info manual. Just 4.7 MB Gzip compressed. It takes some time to load but it's better than the previous man 7 salt thou.

  21. I wish for some easier way of handling inlined images in #GNU #Texinfo.

  22. I wish for some easier way of handling inlined images in #GNU #Texinfo.

  23. I wish for some easier way of handling inlined images in #GNU #Texinfo.

  24. I wish for some easier way of handling inlined images in #GNU #Texinfo.

  25. I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs codeberg.org/rahguzar/filechoo , an Emacs interface to #hoogle codeberg.org/rahguzar/consult-

    There is a (kind of in progress) major mode for #sagemath codeberg.org/rahguzar/sage-mod 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 github.com/sagemath/sage/issue

  26. I have also written an finicky to setup xdg-desktop-portal that let one choose using codeberg.org/rahguzar/filechoo , an Emacs interface to codeberg.org/rahguzar/consult-

    There is a (kind of in progress) major mode for 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) manual for Sage so that I can read it from Emacs github.com/sagemath/sage/issue

  27. I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs codeberg.org/rahguzar/filechoo , an Emacs interface to #hoogle codeberg.org/rahguzar/consult-

    There is a (kind of in progress) major mode for #sagemath codeberg.org/rahguzar/sage-mod 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 github.com/sagemath/sage/issue

  28. I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs codeberg.org/rahguzar/filechoo , an Emacs interface to #hoogle codeberg.org/rahguzar/consult-

    There is a (kind of in progress) major mode for #sagemath codeberg.org/rahguzar/sage-mod 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 github.com/sagemath/sage/issue

  29. I have also written an finicky to setup xdg-desktop-portal that let one choose #files using #emacs codeberg.org/rahguzar/filechoo , an Emacs interface to #hoogle codeberg.org/rahguzar/consult-

    There is a (kind of in progress) major mode for #sagemath codeberg.org/rahguzar/sage-mod 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 github.com/sagemath/sage/issue

  30. Anybody else tried to build #texinfo info pages using #sphinx? What where you experiences? #emacs
    Having offline documentation outside of my browser is very helpful.
    #documentation

  31. Anybody else tried to build #texinfo info pages using #sphinx? What where you experiences? #emacs
    Having offline documentation outside of my browser is very helpful.
    #documentation

  32. Anybody else tried to build #texinfo info pages using #sphinx? What where you experiences? #emacs
    Having offline documentation outside of my browser is very helpful.
    #documentation

  33. Anybody else tried to build #texinfo info pages using #sphinx? What where you experiences? #emacs
    Having offline documentation outside of my browser is very helpful.
    #documentation

  34. Anybody else tried to build #texinfo info pages using #sphinx? What where you experiences? #emacs
    Having offline documentation outside of my browser is very helpful.
    #documentation

  35. @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:

    git.savannah.gnu.org/cgit/guix

    Which would translate to:

    packages.guix.gnu.org/packages

    More info on Texinfo itemization:

    gnu.org/software/texinfo/manua

    And info about marking inline code:

    gnu.org/software/texinfo/manua

    #gnu #guix #texinfo

  36. @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:

    git.savannah.gnu.org/cgit/guix

    Which would translate to:

    packages.guix.gnu.org/packages

    More info on Texinfo itemization:

    gnu.org/software/texinfo/manua

    And info about marking inline code:

    gnu.org/software/texinfo/manua

    #gnu #guix #texinfo

  37. @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:

    git.savannah.gnu.org/cgit/guix

    Which would translate to:

    packages.guix.gnu.org/packages

    More info on Texinfo itemization:

    gnu.org/software/texinfo/manua

    And info about marking inline code:

    gnu.org/software/texinfo/manua

    #gnu #guix #texinfo

  38. @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:

    git.savannah.gnu.org/cgit/guix

    Which would translate to:

    packages.guix.gnu.org/packages

    More info on Texinfo itemization:

    gnu.org/software/texinfo/manua

    And info about marking inline code:

    gnu.org/software/texinfo/manua

    #gnu #guix #texinfo

  39. @plantarum @b0rk @pluralistic I edited some Emacs #texinfo files a couple of times and found it always a bit verbose and quirky, but not really worse than the newer #restructuredText or #asciidoc.

  40. @plantarum @b0rk @pluralistic I edited some Emacs #texinfo files a couple of times and found it always a bit verbose and quirky, but not really worse than the newer #restructuredText or #asciidoc.

  41. @plantarum @b0rk @pluralistic I edited some Emacs #texinfo files a couple of times and found it always a bit verbose and quirky, but not really worse than the newer #restructuredText or #asciidoc.

  42. @plantarum @b0rk @pluralistic I edited some Emacs #texinfo files a couple of times and found it always a bit verbose and quirky, but not really worse than the newer #restructuredText or #asciidoc.

  43. @b0rk I read #info pages all the time from #Emacs when I want to check the documentation on some Emacs functionality or mode (e.g. #orgmode) and the user experience is very similar to a modern readthedocs-style web manuals, just offline. But few people use Emacs and the default terminal `info` program is bad. Even I default to `man` for terminal programs an, checking `info` would not cross my mind except if mentioned in the manpage (which #GNU manpages do). 1/N

    #documentation #texinfo

  44. @b0rk I read #info pages all the time from #Emacs when I want to check the documentation on some Emacs functionality or mode (e.g. #orgmode) and the user experience is very similar to a modern readthedocs-style web manuals, just offline. But few people use Emacs and the default terminal `info` program is bad. Even I default to `man` for terminal programs and checking `info` would not cross my mind except if mentioned in the manpage (which #GNU manpages do). 1/N

    #documentation #texinfo

  45. @b0rk I read #info pages all the time from #Emacs when I want to check the documentation on some Emacs functionality or mode (e.g. #orgmode) and the user experience is very similar to a modern readthedocs-style web manuals, just offline. But few people use Emacs and the default terminal `info` program is bad. Even I default to `man` for terminal programs and checking `info` would not cross my mind except if mentioned in the manpage (which #GNU manpages do). 1/N

    #documentation #texinfo

  46. @b0rk I read #info pages all the time from #Emacs when I want to check the documentation on some Emacs functionality or mode (e.g. #orgmode) and the user experience is very similar to a modern readthedocs-style web manuals, just offline. But few people use Emacs and the default terminal `info` program is bad. Even I default to `man` for terminal programs and checking `info` would not cross my mind except if mentioned in the manpage (which #GNU manpages do). 1/N

    #documentation #texinfo

  47. By the way, GNU Texinfo people seems to be working on new commands to make it easier to structure API documentation 👍

    lists.gnu.org/archive/html/hel

    #gnu #texinfo

  48. By the way, GNU Texinfo people seems to be working on new commands to make it easier to structure API documentation 👍

    lists.gnu.org/archive/html/hel

    #gnu #texinfo

  49. By the way, GNU Texinfo people seems to be working on new commands to make it easier to structure API documentation 👍

    lists.gnu.org/archive/html/hel

    #gnu #texinfo

  50. By the way, GNU Texinfo people seems to be working on new commands to make it easier to structure API documentation 👍

    lists.gnu.org/archive/html/hel

    #gnu #texinfo