* lisp/org-element.el (org-element-timestamp-parser,
org-element-timestamp-interpreter): Add support for repeater
deadlines. Adds two new properties: ':repeater-deadline-value' and
':repeater-deadline-unit'.
* testing/lisp/test-org-element.el (test-org-element/timestamp-parser,
test-org-element/t
On 4/3/24 15:00, Richard H. Stanton wrote:
I just tried to export a single subtree from an org document to a PDF file:
1) Type C-c C-e [org-export-dispatch]
2) C-s to narrow to subtree
3) l -> o to export to PDF via LaTeX
However, instead of exporting the portion of the file I want, I get the
I just tried to export a single subtree from an org document to a PDF file:
1) Type C-c C-e [org-export-dispatch]
2) C-s to narrow to subtree
3) l -> o to export to PDF via LaTeX
However, instead of exporting the portion of the file I want, I get the error
message
Undefined Org macro: newline;
Ihor Radchenko writes:
> It is not very clear when this feature is useful. May you provide a
> small example as a part of the news entry and also
> `org-columns-checkbox-states' docstring?
Yes. You are right. Thank you.
After thinking about I have found a better name:
(defcustom org-columns-che
This is my first contribution guys please be patient if I've got
something wrong. Let me know if the changelog needs more info.
>From 61e18c9e26f6bdbaaff785969881624f9a1c7068 Mon Sep 17 00:00:00 2001
From: Lee Thompson
Date: Wed, 3 Apr 2024 16:20:15 +0100
Subject: [PATCH] ; * doc/misc/org.org (He
Lee Thompson writes:
> I noticed when browsing the info manual for Markdown Export options this
> line concerning headline styles seems to be wrong:
>
>> Header and sectioning structure
>> ---
>>
>> Based on ‘org-md-headline-style’, Markdown export can generate headli
Hi all,
I noticed when browsing the info manual for Markdown Export options this
line concerning headline styles seems to be wrong:
> Header and sectioning structure
> ---
>
> Based on ‘org-md-headline-style’, Markdown export can generate headlines
> of both _atx_ and
Ah, okay. Thank you.
--
: Eric S Fraga, with org release_9.6.23-1314-g945046 in Emacs 30.0.50
"Fraga, Eric" writes:
> So it's a combination of no prefix in such a case and the indentation
> according to major mode. For me, the latter is not an issue but the
> former is.
>
> (but not really an issue for me as I make sure I only have noweb
> references on lines where such a replacement wil
On Saturday, 30 Mar 2024 at 18:34, Visuwesh wrote:
>> Specifically, I would love to make reference to calc variables,
>> especially those defined using embedded calc, in org tables.
>
> Can you please provide a minimal example for me to play around with? I
> realise I would like something like thi
On Friday, 29 Mar 2024 at 09:43, Ihor Radchenko wrote:
> Doerthous writes:
>> #+begin_src elisp
>> (let ((a 0)
>> (let ((b 1))
>>`(,a ,b))
>> #+end_src
>>
>> ~(let (~ is the prefix of <>.
>>
>> I thought we can replace just the prefix in current code[1] with
>> ~(setq prefix (replace-regexp-i
Samuel Wales writes:
> not following this.
>
> but it amused me:
> ...
This is not the final version we settled upon.
https://orgmode.org/worg/org-maintenance.html now has
The assignment process does not always go quickly; occasionally it
may get stuck or overlooked at the FSF. If there
Adam Porter writes:
> 1. Having to use separate BEGIN and END macros is less convenient than
> more Lispy constructs, like a macro call with a string argument. But I
> guess, to wrap Org elements, like a TODO heading or inline task, it
> would be necessary. A macro call with the text as an
Morgan Smith writes:
> * doc/org-manual.org (Plot options): Document "timeind". Also fix the
> formatting for a couple other entries.
Thanks!
Applied, onto bugfix.
https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=3e61311c7
--
Ihor Radchenko // yantar92,
Org mode contributor,
Le
Adam Porter writes:
> I noticed what appears to be a typo in this commit:
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=1be2f9693
>
>
> +*** =.avif= images are not recognized in ~org-html-inline-image-rules~
>^
>
> Unless I misunderstand something,
Max Nikulin writes:
>> This sounds like something to be adapted to Emacs upstream.
>> I suggested to change `string-collate-lessp' fallback behaviour to use
>> `downcase' when IGNORE-CASE is non-nil. See my last message in
>> bug#59275.
>
> I do not share Eli's position "all or nothing". I prefer
16 matches
Mail list logo
