I should have used org-export-select-tags instead of
org-export-exclude-tags. Sorry for the noise.
Julius
Am 26.07.2018 um 18:16 schrieb Julius Dittmar:
> Hi,
>
> I'm still an elisp beginner, so please bear with me.
>
> I would like to be able to fully export org-mode files which make use of
>
Am 29.11.18 um 14:07 schrieb Loris Bennett:
> Eric S Fraga writes:
>
>> On Thursday, 29 Nov 2018 at 09:38, Julius Dittmar wrote:
>>> Am 29.11.18 um 09:13 schrieb Julius Dittmar:
Am 29.11.18 um 08:17 schrieb Loris Bennett:
>> #+latex_header:
>>
Am 05.11.19 um 22:26 schrieb Nathan Neff:
> Hello all,
>
> I know I've asked this before, but can't remember the quick & easy path (TM)
> to creating an org-capture template which will capture to the current
> heading?
prepend the capture command (C-C C in my setting) by C-0
I think it puts the
Am 23.10.19 um 16:18 schrieb Dominik Schrempf:
> I agree with this proposal. At some point I already asked if the following
> structure is possible:
>
> #+begin_example
> * Title
> ** Section I
> Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Donec hendrerit
> tempor
> tellus. Donec
Am 29.10.19 um 16:08 schrieb Julius Müller:
> Am 29.10.19 um 15:57 schrieb Vladimir Nikishkin:
>> Please, consider visitiong M-x info-display-manual RET org RET section
>> 15.2, paragraph 4.
>
> Well, there's at least something missing in that documentation. Without
>
Am 29.10.19 um 15:57 schrieb Vladimir Nikishkin:
> Please, consider visitiong M-x info-display-manual RET org RET section
> 15.2, paragraph 4.
Well, there's at least something missing in that documentation. Without
any config file active, but with org mode loaded, those abbreviations
are not
t; (org-id-get
but how can I add that to the section header?
John Kitchin kindly provided some code to extract the ID at the end of
the metadata block, but unfortunately that's too late for the effect I
am after :-(
Thanks for any pointers,
Julius Müller
Am 18.05.20 um 15:57 schrieb Kaushal Modi:
> I looked through the commits on master in the past month, but I don't
> see any author-specific change that would affect *all* the exporter
> backends.
>
> Can anyone else reproduce this issue?
Same observation here (org master from about a week ago,
Am 31.08.20 um 04:26 schrieb Ihor Radchenko:
> I would not call defining syntax for notes "a syntax change". Rather
> addition to syntax. Since there was no formal definition of notes in the
> past, introducing formal syntax for notes should not break any existing
> tool. If anything, it should
