From: Ihor Radchenko <yantar92@gmail.com>
To: Timothy <tecosaur@gmail.com>
Cc: "Rudolf Adamkovič" <salutis@me.com>, emacs-orgmode@gnu.org
Subject: Re: [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)]
Date: Mon, 04 Jul 2022 20:21:50 +0800 [thread overview]
Message-ID: <8735fhnk4h.fsf@localhost> (raw)
In-Reply-To: <87h73xzjt1.fsf@gmail.com>
Timothy <tecosaur@gmail.com> writes:
> Hi Ihor,
>
> Two comments on this:
>
>> The inline src block defaults should probably be documented. See
>> <https://orgmode.org/list/87ee927emf.fsf@localhost>
>> Patches are welcome.
>
> I think it would also be nice if one could set inline header args with
> `#+properties' and `:PROPERTIES:' in the same manner as block header args.
AFAIK, it is already the case. Only org-babel-default-inline-header-args
is distinct for the inline src blocks. Buffer-local header-args
property, if set, does apply to both inline and normal src blocks.
>> The confusing behavior about exporting results for code blocks when the
>> corresponding ob-*.el is not loaded is trickier. We had a related
>> discussion on this topic in
>> <https://orgmode.org/list/87mtknsdhm.fsf@localhost>
>> Though I am not sure how we can improve the situation. Ideas are
>> welcome.
>
> One of the nice things Doom does with Org is add lazy-auto-loading of ob-*
> backends. I’ve been poking Henrik for a while to upstream this (and a bunch of
> other things) to Org, and am tentatively hopeful it will happen some time this
> year.
Sounds promising :)
Best,
Ihor
prev parent reply other threads:[~2022-07-04 12:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-03 9:57 [BUG] Inline src blocks do not work for LaTeX [9.5.4 (release_9.5.4-3-g6dc785 @ /Users/salutis/src/emacs/nextstep/Emacs.app/Contents/Resources/lisp/org/)] Rudolf Adamkovič
2022-07-03 11:43 ` Ihor Radchenko
2022-07-03 19:11 ` Rudolf Adamkovič
2022-07-03 21:19 ` Christian Heinrich
2022-07-08 20:23 ` Rudolf Adamkovič
2022-07-04 12:08 ` Ihor Radchenko
2022-07-04 2:32 ` Timothy
2022-07-04 12:21 ` Ihor Radchenko [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8735fhnk4h.fsf@localhost \
--to=yantar92@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=salutis@me.com \
--cc=tecosaur@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).