Nicolas Goaziou writes:
> #+include is a keyword specific to export. I doubt it would work with
> tangling out of the box.
>
> However, you may try calling `org-export-expand-include-keyword' from
> `org-babel-pre-tangle-hook'. Untested.
Doom has been doing this for a while with config.org tan
Kyle,
Thanks for the excellent sleuthing. Nailed it.
I took your second suggestion, and ended up with the following (for
those interested), which works like a charm:
=
(setq org-startup-with-inline-images t)
(require 'subr-x)
(defun ded:org-babel-inline-dis
Hi Samuel,
Samuel Wales writes:
> probably not a relevant non-confirmation but in recent maint, my config:
>
> - a
> - /a/
> - b
Thanks for trying. I've uploaded this screencast with a minimal Emacs on
a virtual machine:
https://gnutas.juanmanuelmacias.com/images/org-sort-issue-2021-04-13_15.44
On 10/04/2021 18:41, Juan Manuel Macías wrote:
Nicolas Goaziou writes:
Do you have a simple test case to reproduce the problem? Currently
sorting the following trivial lists causes no issue:
- b
- *a*
and
- *b*
- a
The current result is wrong:
- /a/
- /v/
- a
- b
I c
Hi, Maxim,
Thanks for clearing things up. So it seems obvious that the root
of the problem is in the locales and the collation rules.
The situation is that with locales configured for Spanish from Spain
(en_ES.UTF-8) the list is not ordered correctly, unless those three
spaces from org-sort-remov
* contrib/lisp/org-eldoc.el (org-eldoc-documentation-function): Check
before invoking elisp eldoc functions from Emacs 28.
The previous check assumed that the presence of eldoc 1.11 bindings
implied elisp-mode bindings that come with Emacs>=28, but eldoc 1.11
is available on GNU Elpa so the assu
Should I expect PlantUML source blocks and their resulting images to
be cached and respect `:cache true` ?
In my experience they regenerate every export, even with :cache true.
Thank you
-s
Hi, I was reading the org manual section on source code blocks and I
think there’s a small section where the clarity can be improved.
Section 15.1: Features Overview, first paragraph (line 16396 of org.org)
original: …Users can control how live they want each source code block…
pro
On 2021-04-12 23:38, Nicolas Goaziou wrote:
> However, you may try calling `org-export-expand-include-keyword' from
> `org-babel-pre-tangle-hook'. Untested.
I've done this in the past and can verify that it works well. That said, it by
definition creates cross-talk between org files, with all th
CS Suehs writes:
> Should I expect PlantUML source blocks and their resulting images to
> be cached and respect `:cache true` ?
Yes.
> In my experience they regenerate every export, even with :cache true.
Can you provide an example?
This example caches correctly for me on v9.1.14.
#+name
Nick Daly writes:
> Please see the attached patch that allows for post-processing of
> PlantUML diagrams based on the exported file extension.
If the above patch was too generic and heavy-weight for consideration,
please see this alternative, simpler, patch. It just adds a flag that,
when enable
Rama,
another possible solution, though it may not be possible for your setup,
is to "invert" things: centralize all your snippets in snippet.org, with
each *snippet* set to tangle to its individual lisp file.
cheers, Greg
Thank you, Greg, this is certainly a logical suggestion, but I didn’t explain
why I would have these blocks in individual files - I will explain very quickly
here.
Basically I am developing my Lisp code using the ASDF package manager and so I
have a few different files in a source tree. I haven
Rama writes:
> Ultimately I have just decided that I will develop my code as normal and then
> finally just copy and paste it into orgmode especially since now we can
> select a region and and create a source block around it.
Do you know M-x insert-file? That could simplify your workfloww a lo
Rama,
thanks for your explanation.
Arne Babenhauserheide suggested [M-x org-babel-detangle]; i've not used
it myself, but it seems a possible direction.
cheers, Greg
15 matches
Mail list logo
