flamingos-cant (hopepunk arc)

Webp’s strongest soldier.

  • 53 Posts
  • 133 Comments
Joined 3 years ago
Cake day: June 12th, 2023
  • flamingos-cant (hopepunk arc)@feddit.uktoEmacs@programming.dev•Exporting from orgmodeEnglish
    2·
    1 month ago

    You need to use a symbol, not a string:

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

    write something like this: log_{critical}_{error}

    That’s what you’d need to write to have subscript, with the above set:

    • log_critical => log_critical
    • log_{critical} => logcritical

    ‎

    Edit: org-export-with-superscripts => org-export-with-sub-superscripts

  • flamingos-cant (hopepunk arc)@feddit.uktoEmacs@programming.dev•Exporting from orgmodeEnglish
    1·
    1 month ago

    First of all: how can I turn of the need to manually stop the code execution for code blocks when exporting

    From the docs:

    You can prevent Org from evaluating code blocks for speed or security reasons:

    • To speed up export, use the header argument ‘:eval never-export’
    • For greater security, set the org-export-use-babel variable to nil, but understand that header arguments will have no effect in this case.

    The next thing is, that my function names include underscores, which in orgmode translates to making the following text lowercase.

    Do you mean subscript, like HELLOWORLD? Also from the docs:

    If you write a text where the underscore is often used in a different context, Org’s convention to always interpret these as subscripts can get in your way. Configure the variable org-use-sub-superscripts and/or org-export-with-sub-superscripts to change this convention. For example, when setting these variables to {}, ‘a_b’ is not displayed/exported as a subscript, but ‘a_{b}’ is.

Moderates