stardiviner writes:
> The commands like ~org-next-link~ etc will ignore links in properties
> drawer. I think links in properties drawer should not be ignored.
+1 I agree (and can reproduce).
Rudy
--
"I would prefer an intelligent hell to a stupid paradise."
--- Blaise Pascal
Rudolf Adamkovič
Ihor Radchenko writes:
> May you try the attached patch?
Ihor, you are a magician. It works. Org has never looked better!
Rudy
--
"It is no paradox to say that in our most theoretical moods we may be
nearest to our most practical applications." --- Alfred North
Whitehead, 1861-1947
Rudolf
One more question about `org-babel-execute:latex':
The default value of `org-babel-default-header-args:latex' is
'((:results . "latex") (:exports . "results"))
This means that the result will be wrapped in a `begin_export latex'
block. This is fine when the output of the LaTeX src block is LaTe
> Following up on my previous email about updating
> `org-babel-execute:latex' for the org-latex-preview patchset:
>
> I'm having trouble understanding what header options this function
> supports. Here is a list of relevant header args from the let-bindings
> inside this function. `params' is th
> I suggest adding an optional parameter &optional limit. Then,
> `org-clock-update-mode-line' will pass LIMIT = org-clock-string-limit.
Done, but I renamed the optional parameter to `max-length' for clarity.
> Why "5"?
That accounts for the spaces and parentheses surrounding the headline. I've
Following up on my previous email about updating
`org-babel-execute:latex' for the org-latex-preview patchset:
I'm having trouble understanding what header options this function
supports. Here is a list of relevant header args from the let-bindings
inside this function. `params' is the plist of
I would like to submit the org-latex-preview patchset for review and
merging now. I will be losing my FSF copyright assignment soon, so I'm
hoping to see it merged before then even if there are some minor issues
remaining to be addressed.
Another reason is that the main branch is slowly adding ch
> The patch is not working correctly.
>
> [...]
>
> When I expand all sub-heading. The second link is previewed, but the
> first link DIS-previewed. The correct result should be two links both
> previewed.
As mentioned in my email with the patch, this is a bug with
org-link-beautify:
> Stardivin
Exemple of LaTeX verbatim that lose its special chars when exported to
PDF:
\begin{verbatim}
/test
├── file-a
├── file-b
└── file-c
\end{verbatim}
Jean Louis writes:
> * Sébastien Gendre [2025-03-30 02:48]:
>>
>> I like the `tree` command in a bloc, as I can regenerate it at every
>> direct
Hi again,
Attached is a new version of the patch. It builds on Ihors refactoring
patch.
Best. /PA
On Sun, 30 Mar 2025 at 07:24, Pedro Andres Aranda Gutierrez <
paag...@gmail.com> wrote:
> Thanks!
>
> Will try out as soon as I have time to.
>
> /PA
>
> On Sat, 29 Mar 2025 at 15:44, Ihor Radchenko
The patch is not working correctly.
For example:
*** test(point)
https://www.iamtxt.com/book/48454.html
sub-heading
https://www.iamtxt.com/book/48451.html
When I expand all sub-heading. The second link is previewed, but the first
link DIS-previewed. The correct result should be two links bo
Ashish Panigrahi writes:
> Apologies in advance if this isn't the right mailing list for cdlatex
> related queries (orgmode includes cdlatex hence my choice of the mailing
> list).
Org mode does not include cdlatex. Org mode simply supports it (just as
a number of other third-party packages).
On 2025-03-29, Ihor Radchenko wrote:
> Jens Lechtenboerger writes:
>
>> I want to use the keyword #+include: inside lists to embed source
>> code for HTML export (`C-c C-e h h'), like so:
>>
>> * foo
>> - A list
>> #+include: bar.txt src text
>>
>> Previously, that worked. On Org main, the lis
That a good idea, I will test it.
Ihor Radchenko writes:
> Sébastien Gendre writes:
>
>> In an org-mode document, I have some example blocs. But their text are
>> to long for my LaTeX/PDF export.
>>
>> Is it possible to reduce the size of the font for just some example
>> blocs ?
>
> You may
* Sébastien Gendre [2025-03-30 02:48]:
>
> I like the `tree` command in a bloc, as I can regenerate it at every
> directory modification.
>
> But in the export, all the special chars disappears. It only keep the
> files and directories names.
>
> It must be a problem with LaTeX, as the special
15 matches
Mail list logo
