David Masterson writes:
> Nicolas Goaziou writes:
>
>> Sebastian Miele writes:
>
>>> Sebastian Miele writes:
David Masterson writes:
> Sebastian Miele writes:
>> Currently org-syntax.org says that "TITLE can be made of any
>> character but a new line. Though, it will match
Nicolas Goaziou writes:
> Sebastian Miele writes:
>> Sebastian Miele writes:
>>>David Masterson writes:
Sebastian Miele writes:
> Currently org-syntax.org says that "TITLE can be made of any
> character but a new line. Though, it will match after every other
> part have bee
Hi Nicolas,
Nicolas Goaziou writes:
> You can do it in the same patch.
Here is the updated patch, with the corresponding additions in the
manual and ORG-NEWS.
Best regards,
Juan Manuel
>From 987566d52cd36c990d3db3f83d2c6433254ac2e3 Mon Sep 17 00:00:00 2001
From: Juan Manuel Macias
Date: Tue,
Sorry, maybe I did not test thoroughly enough. I'll do, and come back if
still necessary. thx
Nicolas Goaziou schrieb am Di., 25. Mai 2021,
17:51:
> Michael Dauer writes:
>
> > How do you do this with a #+macro keyword with arguments?
>
> As before, with "(eval ..."
>
> I might be able to give
Adding [PATCH] to the subject so that it appears on updates.orgmode.org.
Hello,
Eric S Fraga writes:
> On Tuesday, 25 May 2021 at 11:59, Denis Maier wrote:
>
> [...]
>
>> With pandoc you can add formatting information to your document
>> metadata, but you can also use makefiles or external files that contain
>> your settings. So, in the end your documents will only
Hello,
Sebastian Miele writes:
> Sebastian Miele writes:
>>David Masterson writes:
>>> Sebastian Miele writes:
Currently org-syntax.org says that "TITLE can be made of any
character but a new line. Though, it will match after every other
part have been matched." This does not
Juan Manuel Macías writes:
> Thank you for your indications. Attached the updated patch.
Thanks.
I forgot to ask: could you add some documentation about it in the
manual, too?
> Do you need me to prepare another patch to document the modifications
> and add them to org-NEWS?
You can do it in
Michael Dauer writes:
> How do you do this with a #+macro keyword with arguments?
As before, with "(eval ..."
I might be able to give you a more specific answer when your question is
more specific, i.e., with an ECM.
Regards,
On Fri, May 21, 2021 at 9:25 AM Bruce D'Arcus wrote:
>
> On Fri, May 21, 2021 at 9:13 AM Nicolas Goaziou wrote:
> > So maybe we should try to converge first. Then, I'll happily implement
> > the result!
>
> Will do; thanks!
Denis Maier and I worked on this off-list.
Below is our suggested revi
Hi Greg,
On 18-05-2021 19:25, Greg Minshall wrote:
> Lennart,
>
> John's idea seems good. also, you could generate a separate RESULT for
> each language, then :var each language's "failed" RESULT into your bash
> block and fail if any of them are set?
The main problem I see with that solution i
Dear John,
Thanks a lot for your quick reply. My apologies for not replying
earlier. Some urgent things came up that took my time.
I tried your suggestions and settled on a small adaptation of your first
suggestion. Because the output of my source blocks is raw Org code (i.e.
the report text that
Hi Nicolas,
Thank you for your indications. Attached the updated patch.
Do you need me to prepare another patch to document the modifications
and add them to org-NEWS?
Best regards,
Juan Manuel
Nicolas Goaziou writes:
> Hello,
>
> Juan Manuel Macías writes:
>
>> Subject: [PATCH] ox-latex.el
On Tuesday, 25 May 2021 at 11:59, Denis Maier wrote:
[...]
> With pandoc you can add formatting information to your document
> metadata, but you can also use makefiles or external files that contain
> your settings. So, in the end your documents will only contain the contents:
[...]
> How do
How do you do this with a #+macro keyword with arguments?
The old implementation checked the string for a "(eval" prefix.
Nicolas Goaziou schrieb am Di., 25. Mai 2021,
11:14:
> Hello,
>
> Michael Dauer writes:
>
> > at least not compatible with before.
> >
> > Probably caused by commit 8abdbbe
Sebastian Miele writes:
>David Masterson writes:
>> Sebastian Miele writes:
>>> Currently org-syntax.org says that "TITLE can be made of any
>>> character but a new line. Though, it will match after every other
>>> part have been matched." This does not reflect the currently
>>> effective beha
Hi David and all,
David Masterson writes:
> Sebastian Miele writes:
>> Currently org-syntax.org says that "TITLE can be made of any
>> character but a new line. Though, it will match after every other
>> part have been matched." This does not reflect the currently
>> effective behavior that "*
Hi everyone,
given the recent developments regarding the citation syntax I'm
currently looking at orgmode as a writing environment again. One thing I
don't understand currently: Do you have to have you export configuration
in your source file or is there a way to keep your writing clean from
Hello,
Juan Manuel Macías writes:
> Subject: [PATCH] ox-latex.el: add LaTeX attributes to quote block
Thank you. Some comments follow.
> +(defcustom org-latex-default-quote-environment "quote"
> + "Default environment used to `quote' environment."
--> Default environment used for "quote" bl
Hello,
Michael Dauer writes:
> at least not compatible with before.
>
> Probably caused by commit 8abdbbee395f284f2262a89187d662eaf40080b1.
>
> originally correct macro ("macroA" . "(eval
> do-something-dynamically-at-macro-expansion)")
>
> How should this be achieved now? (functionp "any-string
Tim Cross writes:
> Julien Cubizolles writes:
>
>> I'm using a custom python program to display x11 idle time. I've set
>> org-clock-x11idle-program-name accordingly but org-x11idle-exists-p is
>> still nil. I'm guessing it's defvar'ed in org-clock.el before
>> org-clock-x11idle-program-name is
21 matches
Mail list logo
