zzamboni’s avatarzzamboni’s Twitter Archive—№ 4,826

  1. …in reply to @gumnos
    @gumnos @cmdln_ @unix_ninja @BasementTrix If the source is in org-mode, you normally don't even need pandoc, since there are good exporters for pretty much anything. The new edition of my book is in org-mode (was a PAIN to semi-manually convert from Asciidoc to Org-mode), from which I can generate whatever I need.
    1. …in reply to @zzamboni
      @gumnos @cmdln_ @unix_ninja @BasementTrix For example at the moment I use Leanpub-Flavored Markdown, but it has some limitations for tables, so I'm working on an exporter for Markua, so I can reintroduce @atsaloli's appendix with the attribute description tables.
      1. …in reply to @zzamboni
        @gumnos @cmdln_ @unix_ninja @BasementTrix @atsaloli BTW @cmdln_ : would you consider a PR that includes descriptions of each attribute in the output of cf-promises --syntax-description --json? Would be awesome for auto-generating those tables, and also to support eldoc in Emacs and similar stuff in other editors/IDEs
        1. …in reply to @zzamboni
          @gumnos @cmdln_ @unix_ninja @BasementTrix @atsaloli Or would it be too much text to include in the binary? It's cf-promises, not cf-agent, so I am hopeful.
          1. …in reply to @zzamboni
            @gumnos @cmdln_ @unix_ninja @BasementTrix @atsaloli @atsaloli would you agree? I am halfway through a script that extracts the description from the Asciidoc text of your appendix and inserts it into the JSON produced by --syntax-description :)