[BUG] org-icalendar-include-todo keyword doesn't include entries with keyword [9.7-pre (release_9.6.8-785-g72bbf8.dirty @ /home/bidar/.local/private/etc/emacs/lib/org/lisp/)]

2023-10-21 Thread Björn Bidar
* Description I'm using org-caldav, I wanted to exclude todo without those that don't have states that are not mapped to vtodo percent states. So I tried to set org-icalendar-include-todo to include only those with the todo states I want but that doesn't seem to work. Either I select the other

Re: Feature request: export form feed as page break

2023-10-21 Thread Marvin Gülker
Am Samstag, dem 21. Oktober 2023 schrieb Ihor Radchenko: > In general, adding page breaks can make sense. The main concern is that > the location of page breaks may or may not be export > backend-independent. In certain scenarios, you may need to put page > breaks in one place for odt export,

Re: Feature request: export form feed as page break

2023-10-21 Thread Marvin Gülker
Am Samstag, dem 21. Oktober 2023 schrieb Max Nikulin: > As a workaround you may define an Org macro that expands to > @@latex:\newpage@@ and appropriate XML element inside @@odt:…@@. Fair enough, this is possible, but then I have to consider each backend I may export to and read up on how the

Re: Feature request: export form feed as page break

2023-10-21 Thread Max Nikulin
On 21/10/2023 16:19, Ihor Radchenko wrote: - page breaks location is very much backend-dependent; typographic detail https://list.orgmode.org/orgmode/875yhiyxnb.fsf@localhost Is the link correct? Ihor Radchenko to emacs-orgmode… Re: FR: support hard-newlines [9.5.5 (release_9.5.5 @

Re: Feature request: export form feed as page break

2023-10-21 Thread Max Nikulin
On 21/10/2023 14:42, Marvin Gülker wrote: However, for the page break I always need to write a literal \newpage into the document, which does work, but only in LaTeX. As a workaround you may define an Org macro that expands to @@latex:\newpage@@ and appropriate XML element inside @@odt:…@@.

Re: Case insensitivity of simple [[links]]

2023-10-21 Thread Ihor Radchenko
Rudolf Adamkovič writes: > Ihor Radchenko writes: > >> [...] loading happens before Emacs loads file-local variables. This is >> by major mode design and we cannot do much about this. See >> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57003 > > I see. So, that is by design of Emacs, and Org

Re: [PATCH] Fix obsolete sleep-for usage

2023-10-21 Thread Ihor Radchenko
gerard.vermeu...@posteo.net writes: > Emacs-30 obsoletes the second integer 'millisec' argument of > 'sleep-for' > and tells to use a float argument. This patch fixes the obsolete usage. Thanks! Applied, onto main, with amendments to the commit message.

Re: Feature request: IDs for everything

2023-10-21 Thread Ihor Radchenko
Tor Erlend Fjelde writes: > I was wondering if there's a reason why we couldn't have IDs a la > org-id.el for everything? It seem to me that it would be useful to use > something like `#+ID` in place of `#+NAME` for tables, blocks, etc. as > well as headlines. This has been discussed in the

Re: Case insensitivity of simple [[links]]

2023-10-21 Thread Rudolf Adamkovič
Ihor Radchenko writes: > [...] loading happens before Emacs loads file-local variables. This is > by major mode design and we cannot do much about this. See > https://debbugs.gnu.org/cgi/bugreport.cgi?bug=57003 I see. So, that is by design of Emacs, and Org has no built-in mechanism, akin to

No-description <> links

2023-10-21 Thread Rudolf Adamkovič
Hello there! Consider the sentence "This is a [[link]]." in a document with a "<>" target. Org exports the sentence to HTML as "This is a No description for this link." and to PDF as "This is a ." How about we export it as "This is a link." where the word "link" is the actual

[PATCH] Fix obsolete sleep-for usage

2023-10-21 Thread gerard . vermeulen
Hi, Emacs-30 obsoletes the second integer 'millisec' argument of 'sleep-for' and tells to use a float argument. This patch fixes the obsolete usage. Regards -- Gerard 0001-Fix-obsolete-sleep-for-usage.patch Description: Binary data

Re: Colons in :var header arguments

2023-10-21 Thread Ihor Radchenko
Stefano Ghirlanda writes: > I have run into an inconvenience in that colons in :var header > arguments to source blocks are invariably interpreted as referring to > another file. However, I use cleveref in LaTeX export (via org-ref) to > automatically format references using labels like

Re: Feature request: export form feed as page break

2023-10-21 Thread Ihor Radchenko
Marvin Gülker writes: > > To ease this process, I would like to request that the ASCII control > character U+000C FORM FEED (displayed by emacs as ^L and also known as > `\f' in C string notation) is recognised by exporters and translated to > the corresponding page break command, that is,

Re: Feature request: IDs for everything

2023-10-21 Thread Tor Erlend Fjelde
> What could be the added benefits of having such a header argument? I can > think of this benefit: #+NAME would be used for referencing them through a > human-friendly name and the name could change and the #+ID would be an UUID > that is not expected to change. This is indeed one use-case I

[TASK] Allow customizeable ditaa executable in ob-ditaa.el (was: org-ditaa woes)

2023-10-21 Thread Ihor Radchenko
"Dr. Arne Babenhauserheide" writes: >>> In my current source I see [...] >>> >>> (use C-h v org-babel-ditaa-java-cmd to see the value of the java >>> executable — you can then customize this to use a different command) >> >> As far as I understand that part of code it still kind-of assumes that

Feature request: export form feed as page break

2023-10-21 Thread Marvin Gülker
Dear list, I am creating training material for the education of German law students, which usually consists of a case story on one or two pages, followed by a page break after which a proposal for resolving the case is provided. The structure is like this because usually I provide the case story

Re: org-ditaa woes

2023-10-21 Thread Dr. Arne Babenhauserheide
Florin Boariu writes: > Replying to Arne's comment: > >> In my current source I see [...] >> >> (use C-h v org-babel-ditaa-java-cmd to see the value of the java >> executable — you can then customize this to use a different command) > > As far as I understand that part of code it still kind-of