Hi all,
I would like my source blocks to be exported to HTML as textareas with a
class attribute -- so I can later use this in my javascript code. I can
use ":textarea t" [1], but it seems that other attributes except width
and height are ignored:
#+ATTR_HTML: :textarea t :class testing
#+BE
> On Wed, 2 Oct 2019 09:31:33 +, "Fraga, Eric" said:
Eric> On Tuesday, 1 Oct 2019 at 23:38, Nathan Neff wrote:
>> I have a meeting that's scheduled from 10:00 - 11:00 for the next three
>> days.
Eric> This is discussed in the FAQ on the org mode website.
Eric> Quick
Hi all,
in my org files I've got something like:
#+export_file_name: PDF/2019_MY_PRESENTATION
but I've seen that if the containing folder (PDF) is not there there
is no way to generate the file at all. Is there any toggle to
instrument org to create the directory if it does not exist?
Also, any c
"Fraga, Eric" writes:
> Hi Adam,
>
> I've had a chance to play with it a little bit. Works very well
> generally. Some notes:
Hi Eric,
> - a way to exit the sidebar-tree mode to get back to the full buffer
> (e.g. to run commands that require the whole file). The documentation
> seems to
Marco Wahl writes:
> You say the visibility is better for the #+-property keywords. I say
> they can occur _anywhere_ in the file and even in some drawers. See
> above "#+CATEGORY: cat-doc-prop-keyword-2".
>
> Further you say
>
- However, it seems to me that the simplest, most natural pr
Hi Gustav,
Gustav Wikström writes:
> I'd argue that precedence already works that way. One has to take
> inheritance into account. With inheritance turned on, tell me which
> value for Property1 is used for the nodes in the following example:
>
> #+begin_src org
> ,* Node 1
> ,* Node 2
> :
On Thu 19-Sep-2019 at 21:39:10 +02, garj...@garjola.net wrote:
> Hi,
>
> I like the warning in the mode line when the time clocked on a task goes
> beyond the effort estimates in the properties drawer.
>
> However, I don’t know how to use this for repeating tasks or habits.
> That is, I want to wo
