So, I started to use orgmode for writing the documentation for my latest software project. This means, that I have code blocks and lots of special characters in my document. I will have to export this whole file to LaTex/pdf, so my colleague can bind it into his project documentation and this is exactly where my problems are. First of all: how can I turn of the need to manually stop the code execution for code blocks when exporting? I have the single line src_bash{} blocks but also the multiline versions:

#+begin_src bash :
#code
#+ends_src

The next thing is, that my function names include underscores, which in orgmode translates to making the following text lowercase. I tried using \ to escape it, but that only breaks it in a new way and I seriously cant comprehend how this so called zero width space is supposed to be used.

  • da_cow (she/her)@feddit.orgOP
    link
    fedilink
    arrow-up
    1
    ·
    1 day ago

    So I have set them like this:

    (setq org-use-sub-superscripts '{}
    
          org-export-with-superscripts '{})
    

    and it still does not render correctly. Writing log_critical and log_{critical} gets rendered as logcritical

    • flamingos-cant (hopepunk arc)@feddit.uk
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      1 day ago

      Weird, are they getting overridden by something else in your config (a package or something). In an org-mode buffer, what’s the output of C-h v org-export-with-sub-superscripts?

      Edit: worked out the issues, I wrote the one of the variable names wrong, it should be org-export-with-sub-superscripts not org-export-with-superscripts

      • da_cow (she/her)@feddit.orgOP
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        That fixed it. :3

        May I ask you something else? Do you know how I can configure the layout of tables in Orgmode? Currently my table looks like this:

        What I am missing is a separator between each column. I tried out various things through the LaTex attributes as it has been described here, but most stuff either broke my caption or didnt change anything at all about the table. I have not configured my table anything beyond giving it a caption.