Re: Properties drawer at buffer/file level

2024-07-31 Thread Martin Edström
The property drawer has to come first for technical reasons. Just try manually moving the property drawer beneath the title, then do M-: (org-entry-get nil "ID") and what do you get? Nil. Martin On Mon, 29 Jul 2024 18:02:35 +0200, Sébastien Gendre wrote: > Hello, > > > If I set a prop

Re: Properties drawer at buffer/file level

2024-07-29 Thread Sébastien Gendre
"Martin Edström" writes: > Bit off-topic, but I have still not understood what functionality the > file-level drawers actually enable. I suppose dropping support is out > of the question? It seems every other function I write has to have > special-purpose code to handle the case of outline level

Re: Properties drawer at buffer/file level

2024-07-29 Thread Martin Edström
That's why the command puts them at the top. That's where it'll work. As for changing it so they can be below the title, a question is how far below? Realize that #+keywords can actually be anywhere in the document, interspersed with body text. We'd at least need something like an `org-end-of

Re: Properties drawer at buffer/file level

2024-07-29 Thread Sébastien Gendre
I get nil. "Martin Edström" writes: > The property drawer has to come first for technical reasons. Just try > manually moving the property drawer beneath the title, then do > > M-: (org-entry-get nil "ID") > > and what do you get? Nil. > > Martin > > On Mon, 29 Jul 2024 18:02:35 +0200,

Re: Properties drawer at buffer/file level

2024-07-29 Thread Martin Edström
The property drawer has to come first for technical reasons. Just try manually moving the property drawer beneath the title, then do M-: (org-entry-get nil "ID") and what do you get? Nil. Martin On Mon, 29 Jul 2024 18:02:35 +0200, Sébastien Gendre wrote: > Hello, > > > If I set a property