Re: Bug: unexpected behavior of nesting braces when exporting to LaTeX

Hello Yue, On Friday, 20 Aug 2021 at 00:45, Chlo De wrote: > \emph{{n+1}-a} > \textit{a{b}c} > > will be translated as LaTeX expressions > > \emph\{\{n+1\}-a\} > \textit\{a\{b\}c\} I'm not sure it is a bug. Could you specify what do you expect in these cases? Note that there are native org-

Issues with the hanging package used by org-cite

Hi All, I’ve come across an issue with the `hanging' package we’re currently using for LaTeX exports — it also affects punctuation, and makes `,.'"`?!:;' active characters throughout the entire document. That means a LaTeX snippet like: ┌ │ \(f'(x)\) └ Will now fail to compile ☹. See

Testing if a scheduled date is prior to another date

Hi, in a capture template, I want to test whether the scheduled date for a specific task is prior to another, calculated date (and depending on the answer, insert a checkbox or not). I can get the scheduled date for the task by: | (with-current-buffer (find-file-noselect "/path/to/file.org") |

Re: S-M-{,} on CLOCK timestamp

Hello Tim! Em [2021-08-22 dom 11:21:47+1000], Tim Cross escreveu: > I cannot reproduce this. > > When I do the same, I don't see any change in Task A's timestamp at all. > There must be some other setting in play here which I don't have. I am sorry, my description of the initial condition was in

Re: Bug: unexpected behavior of nesting braces when exporting to LaTeX

Hello Yue, Posting your mail below back to the list where you have a better chance of getting the right explanation. I totally understand that many times copy directly latex chunk is a nice feature org-mode offers. >From your example below, exporting the following script to latex would work ok in

Bug: inconsistent handling of empty duration cells in table [9.4.6 (9.4.6-12-gdcc3a8-elpa @ /home/jet/.config/emacs/elpa/org-20210816/)]

When calc formulas producing empty strings are evaluated in the default mode, an empty cell is produced. When evaluated in duration mode (U, T, or t) a zero duration is produced. I feel the behavior should be consistent with the number formats, producing a empty value instead of a zero. Test case:

Re: Bug: File variable no longer on first line when running org-id-get-create [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]

I would argue this is an org-roam bug rather than an org bug and so needs to be reported to the org-roam maintainers. org-roam is not part of org mode. Peter Prevos writes: > Hi, I use file variables on the first line of some Org mode files to indicate > the local Flyspell dictionary, e.g.: >

Re: Internal link broken when publishing (was org-id with ox-html)

Links between two different files, like `[[id:e54113f9-2ad7-4a86-94be-68ffc696de0b][hello]]`, get broken when publishing. (whatever the settings). I haven't found any workaround. Being able to move around entries, functionality provided by `org-id-link-to- org-use-id`, is pivotal, IMO.

Re: Bug: File variable no longer on first line when running org-id-get-create [9.4.4 (release_9.4.4 @ /usr/share/emacs/27.2/lisp/org/)]

Peter Prevos writes: > -*- mode: org; ispell-local-dictionary: "nederlands" -*- > > It works great, except when I need to add an ID for use in > Org-Roam using the org-id-get-create function. To make it work, convert the local-var line into proper comment. Just as you would do in any other sour