From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Re: org-depend: TRIGGER XYZ(KEYWORD) not working
Date: Mon, 4 Dec 2017 20:21:30 +0100 [thread overview]
Message-ID: <2017-12-04T20-17-40@devnull.Karl-Voit.at> (raw)
In-Reply-To: CAMYmr8yqKd22byz0TF_99Z0Nst6TXe8B7FQ5FoAbcTThtpK72g@mail.gmail.com
Hi Adrian,
* Adrian Bradd <adrian.bradd@gmail.com> wrote:
>
>> Examples:
>>
>> * Top-Heading
>>
>> ** TODO Here I invoke org-todo to DONE
>> :PROPERTIES:
>> :TRIGGER: 2017-12-03-target(TODO)
>> :END:
>>
>> ** This should be changed to TODO
>> :PROPERTIES:
>> :ID: 2017-12-03-target
>> :END:
>>
>> ... this is working (i.e., "This should be changed to TODO" gets its
>> TODO keyword).
>>
>> * Top-Heading with process indicator [0/2]
>>
>> ** TODO Here I invoke org-todo to DONE
>> :PROPERTIES:
>> :TRIGGER: 2017-12-03-target(TODO)
>> :END:
>>
>> ** This should be changed to TODO
>> :PROPERTIES:
>> :ID: 2017-12-03-target
>> :END:
>>
>> ... this is *not* working.
>>
>> However, anticipating the wrong position:
>>
>> * Top-Heading with process indicator [0/2]
>> :PROPERTIES:
>> :TRIGGER: 2017-12-03-target(TODO)
>> :END:
>>
>> ** TODO Here I invoke org-todo to DONE
>> :PROPERTIES:
>> :TRIGGER: 2017-12-03-target(TODO)
>> :END:
>>
>> ** This should be changed to TODO
>> :PROPERTIES:
>> :ID: 2017-12-03-target
>> :END:
>>
>> ... is working. And according to this:
>>
>> * Top-Heading with process indicator [0/2]
>> :PROPERTIES:
>> :TRIGGER: 2017-12-03-target(TODO)
>> :END:
>>
>> ** TODO Here I invoke org-todo to DONE
>>
>> ** This should be changed to TODO
>> :PROPERTIES:
>> :ID: 2017-12-03-target
>> :END:
>>
>> ... this is also working. So the update of the process indicator
>> causes the wrong property drawer to be parsed for the relevant
>> TRIGGER property.
>>
>> Contrary to my previous assumption, this is issue is *not* related
>> to big and small files. This is purely related to the existing or
>> missing process indicator of the upper-level heading.
>>
>> I guess I have found the origin of the bug.
>
>
> I'm not able to reproduce what you are seeing above.
Damnit.
This is because I removed the wrong progress indicator from my
examples before posting. You have to change all "[0/2]" with "[%]"
and then you see the issue I described. It seems to be the case that
[/] do work whereas [%] do cause the described malfunctional
behaviour. I was using both and did remove the wrong one.
> I did see an issue with triggered headings not honouring note logging when
> the todo was set to DONE, but I haven't looked any closer at it just yet.
Oh.
> What version of org-mode are you running? If you are using the git version
> can you pull the latest on maint. I performed my testing on maint.
I was using git maint from a couple of days ago and I just updated
the repository.
> =E2=80=8BEven just being able to dig through some code and debug can be a m=
> ajor
> benefit. :-)
And I got the feeling that I learned more about how the elisp code
is working. I should do more debugging even for working code ;-)
--
get mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML into Org-mode:
> get Memacs from https://github.com/novoid/Memacs <
Personal Information Management > http://Karl-Voit.at/tags/pim/
Emacs-related > http://Karl-Voit.at/tags/emacs/
next prev parent reply other threads:[~2017-12-04 19:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 10:05 org-depend: TRIGGER XYZ(KEYWORD) not working Karl Voit
2017-11-19 10:18 ` Karl Voit
2017-12-03 15:13 ` Adrian Bradd
2017-12-03 18:38 ` Karl Voit
2017-12-04 2:42 ` Adrian Bradd
2017-12-04 19:21 ` Karl Voit [this message]
2017-12-06 2:51 ` Adrian Bradd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2017-12-04T20-17-40@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).