Re: [PATCH] Run latex more than once for LaTeX src block evaluation

>> Thanks for the patch! >> May you please describe a use case when it is necessary to run >> latex >> multiple times for previews? > > Sure: it's required whenever you have LaTeX that refers to > other document elements whose positions are only known after > they've been typeset. This often comes

Re: [PATCH] Run latex more than once for LaTeX src block evaluation

Oh-- and pass `processing-type' to `org-create-formula-image' explicitly. -- Michael

Re: [PATCH] Run latex more than once for LaTeX src block evaluation

Ihor Radchenko writes: Michael writes: Should we perhaps have different variables for preview & Org source block evaluation? Likely yes. In fact, ob-latex is making use of `org-preview-latex-process-alist' only in a single cond branch in `org-babel-execute:latex' - when we have :file

Re: Better support admonitions blocks

Hi Ihor, JD, et al, On 4/4/24 12:04, Ihor Radchenko wrote: JD Smith writes: Pandoc recently added read/write support for "admonitions", which are a GFM construct already supported by other org-ex

Re: [PATCH] lisp/org-element.el: Add repeater-deadline support to org-element

Hello, Thanks for the review! See two patches attached. One for org and one for worg. Tests still pass on my end. Ihor Radchenko writes: > Please also add etc/ORG-NEWS entry - it is org-element API change. Done > In addition to changes in Org git, you also need to update > https://orgmode.

Re: Radio links work only in small numbers

Ihor Radchenko writes: > Thanks for testing! > Applied, onto main. > https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=341a01a07 > Fixed. Thanks everyone for chiming in and fixing the problem. I have been unexpectedly busy lately, hence the radio silence [pun intended]. Great wor

Re: Has VISIBILITY property become case-sensitive?

Actually, it didn’t! But now I’m not seeing the original behavior either, though I haven’t changed anything. Don’t spend any more time on this - I’ll report back if I learn anything else. Best Richard > On Apr 4, 2024, at 12:42 PM, Richard Stanton wrote: > > Here’ s a very simple org fil

Re: [PATCH] org-faq.org: rename org-export-htmlize-* options to org-html-htmlize-*

Ihor Radchenko writes: While you are on it, ... > +Normally, when you export an agenda view from within emacs, htmlize > +will convert your face definitions to direct color css styles inlined emacs -> Emacs (per English, and to match Org in the same sentence) css -> CSS (per English, and to mat

Re: Has VISIBILITY property become case-sensitive?

Here’ s a very simple org file that exhibits the behavior I describe - #+STARTUP: overview * Hidden - This should not initially appear - Nor this * Visible :PROPERTIES: :VISIBILITY: content :END: - This should appear - And this ——— Change the case of the word “VISIBILILTY”

Re: Has VISIBILITY property become case-sensitive?

Richard Stanton writes: > My org file has the header line > > #+STARTUP: overview > > One section contains the properties drawer > > :PROPERTIES: > :Visibility: content > :END: > > This used to show the contents of that subtree on first loading the file, but > it no longer does. Experimentation

Re: [BUG] Org export fails on $k$-ary

Jens Lechtenboerger writes: > I would expect this to be exported to HTML and LaTeX correctly: > "A $k$-ary function has $k$ arguments" > > In 12.5.1 LaTeX fragments, this use of a hyphen is documented: > "To avoid conflicts with currency specifications, single ‘$’ > characters are only recognize

Has VISIBILITY property become case-sensitive?

My org file has the header line #+STARTUP: overview One section contains the properties drawer :PROPERTIES: :Visibility: content :END: This used to show the contents of that subtree on first loading the file, but it no longer does. Experimentation shows that it works if I change “Visibility”

Re: How to export a single subtree but include document preamble?

On 4/4/24 14:11, Richard Stanton wrote: Thanks for the suggestion! It would still be nice (i.e., you wouldn’t have to do this for every section you ever want to export) to have a way of specifying a line that gets executed for EVERY (say) LaTeX export. Or else an option to do something like inc

Re: How to export a single subtree but include document preamble?

On Apr 4, 2024, at 11:11 AM, Richard Stanton wrote: > >> I don't know if this does what you want, but I use a ‘PROPERTIES’ drawer >> right below the subtree's headline and in that drawer, I put the following >> code: >> >> :EXPORT_LATEX_HEADER_EXTRA: \input{latex-preamble.tex} >> >> Scott Ran

Re: [FR] 'org-columns-next-allowed-value' for 'summary-checkbox'es functions should have 'intermediate state' '[-]'

Ihor Radchenko writes: > Do not forget to add :package-version. Thank you for bringing it to my attention. Patch in attachment. >From eb71166693065534be9effdc28aea54bb24e64d2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?S=C5=82awomir=20Grochowski?= Date: Sat, 16 Mar 2024 13:29:53 +0100 Subject:

Re: How to export a single subtree but include document preamble?

> I don't know if this does what you want, but I use a ‘PROPERTIES’ drawer > right below the subtree's headline and in that drawer, I put the following > code: > > :EXPORT_LATEX_HEADER_EXTRA: \input{latex-preamble.tex} > > Scott Randby Thanks for the suggestion! It would still be nice (i.e.,

[BUG] Org export fails on $k$-ary

Dear all, I would expect this to be exported to HTML and LaTeX correctly: "A $k$-ary function has $k$ arguments" In 12.5.1 LaTeX fragments, this use of a hyphen is documented: "To avoid conflicts with currency specifications, single ‘$’ characters are only recognized as math delimiters if the enc

Re: Better support admonitions blocks

JD Smith writes: > Pandoc recently added read/write support > for "admonitions", which are a > GFM construct already > supported by other org-exporters, and on GH in markdown. This refcard >

Re: [PATCH] lisp/org-element.el: Add repeater-deadline support to org-element

Morgan Smith writes: > I would like to add some features to org-habit (something I have tried > unsuccessfully in the past). Before I do that, I would like to switch > org-habit over to the org-element api. Before I do that, I would like to > extend org-element to support the org-habit syntax.

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

Rudolf Adamkovič writes: > > +1 for the full name. > > Searching 'M-x' for 'region' gives 229 results on my Emacs, so there is > a precedent. In fact, when I first read the name 'reglock', I took > 'reg' for *not* a region, but register or registry, precisely because > Emacs consistently spell

Re: Pending contents in org documents (Re: Asynchronous blocks for everything (was Re: ...))

Ihor Radchenko writes: > Bruno Barbier writes: > >> I've pushed an update that should address most of your comments. > > Thanks! > >> I've found a better name: I'm now calling it a "lock". So I renamed >> "PENREG" into "REGLOCK" as "region lock". The structure is now >> `org-pending-reglock'.

Re: [FR] 'org-columns-next-allowed-value' for 'summary-checkbox'es functions should have 'intermediate state' '[-]'

Sławomir Grochowski writes: > After thinking about I have found a better name: > ... > What do you think? Looks reasonable. > (defcustom org-columns-checkbox-allowed-values '("[ ]" "[X]") > "Allowed values for column with SUMMARY-TYPE that use checkbox." > :group 'checkbox > :type '(repe

Re: [PATCH] doc/misc/org.org: Corrected info mixup.

Lee Thompson writes: > This is my first contribution guys please be patient if I've got > something wrong. Let me know if the changelog needs more info. Applied, onto bugfix, with minor amendments to the commit message. I removed the "." at the end of the commit summary and removed ";" - we do n

Better support admonitions blocks

Pandoc recently added read/write support for "admonitions", which are a GFM construct already supported by other org-exporters, and on GH in markdown. This refcard

Re: [PATCH] org-faq.org: rename org-export-htmlize-* options to org-html-htmlize-*

Ihor Radchenko writes: > dongdigua writes: > >> sorry, my email client wrapped the lines > > Thanks! > I looked into this again, and I can see that the FAQ entry is dubious. > ... > So, we need a much more significant rewrite to make this FAQ entry up to > date. See the attached alternative ver

Re: Inactive timestamps show up in agenda

On Thu, 4 Apr 2024 at 13:01, Ihor Radchenko wrote: > > Michael Maurer writes: > > > Both <2024-04-04 Do> and [2024-04-04 Do] show up in Agenda-View. > > Google couldn't really help me on that, and I'm thinking maybe there's > > a flag I set to include every timestamp in Agenda? I don't know. > >

Re: Inactive timestamps show up in agenda

Michael Maurer writes: > Both <2024-04-04 Do> and [2024-04-04 Do] show up in Agenda-View. > Google couldn't really help me on that, and I'm thinking maybe there's > a flag I set to include every timestamp in Agenda? I don't know. > > For reference, the entries look like this: > * TEST > <2024-04-

Inactive timestamps show up in agenda

Both <2024-04-04 Do> and [2024-04-04 Do] show up in Agenda-View. Google couldn't really help me on that, and I'm thinking maybe there's a flag I set to include every timestamp in Agenda? I don't know. For reference, the entries look like this: * TEST <2024-04-04 Do> [2024-04-04 Do] shows as Thu