And I should add - the cause of :LOGBOOK: being above :PROPERTIES: on
those particular tasks may be a bug in an Asana-to-Org converter I
wrote, rather than org itself. So I apologize doubly for the noise.
John
On 10/11/2017 07:46 AM, John Goerzen wrote:
> On 10/11/2017 01:55 AM, Eric S Fraga wro
On 10/11/2017 01:55 AM, Eric S Fraga wrote:
> On Tuesday, 10 Oct 2017 at 22:01, John Goerzen wrote:
>> I cannot make it misbehave with either SCHEDULED or CLOSED in my testing
>> now.
> Maybe try org-lint to see if there are more subtle errors in your
> file(s)?
>
Ah ha! So it looks like the real
On Tuesday, 10 Oct 2017 at 22:01, John Goerzen wrote:
> I cannot make it misbehave with either SCHEDULED or CLOSED in my testing
> now.
Maybe try org-lint to see if there are more subtle errors in your
file(s)?
--
: Eric S Fraga via Emacs 27.0.50, Org release_9.1.2-98-g0b8316
signature.asc
Des
On 10/10/2017 08:42 PM, Richard Lawrence wrote:
> Hi John,
>
> John Goerzen writes:
>
>> Unfortunately, org-mode only recognizes the PROPERTIES when they
>> occur immediately after the headline. So whenever I take an action
>> on an item like this, the properties become invisible to org-mode.
Hi John,
John Goerzen writes:
Unfortunately, org-mode only recognizes the PROPERTIES when they
occur immediately after the headline. So whenever I take an
action on an item like this, the properties become invisible to
org-mode.
What version of Org are you running? This sounds like ol
So I have a lot of cases where there is a :PROPERTIES: drawer. It
contains, crucially, an ID (I use those for linking). When I close a
task with C-c C-t and pick DONE, or when I schedule it with C-c C-s, it
will insert CLOSED: or SCHEDULED: lines ABOVE the :PROPERTIES: line.
Unfortunately, org-m
