From: Colin Baxter <m43cap@yandex.com>
To: Josh Moller-Mara <jmm@cns.nyu.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Marking repeated tasks with two tags as DONE causes problems
Date: Fri, 11 Aug 2017 08:27:33 +0100 [thread overview]
Message-ID: <87tw1e36oq.fsf@yandex.com> (raw)
In-Reply-To: <87zib660wq.fsf@cns.nyu.edu> (Josh Moller-Mara's message of "Fri, 11 Aug 2017 15:04:05 +0800")
Dear Josh,
>>>>> "Josh" == Josh Moller-Mara <jmm@cns.nyu.edu> writes:
Josh> Hello,
Josh> I'm starting to encounter a strange, silent problem when
Josh> switching the state of a task with multiple tags. With the
Josh> following minimal example:
Josh> #+STARTUP: logdone #+STARTUP: logdrawer
Josh> * TODO Hello :hi:there: SCHEDULED: <2017-08-11 Fri .+1d>
Josh> Switching The "hello" task from "TODO" to "DONE" should keep
Josh> the task as "TODO", but schedule it in the future. Instead,
Josh> the file ends up looking like:
Josh> #STARTUP: logdone :hi:there:
Josh> #+STARTUP: logdrawer * DONE Hello :hi:there:
Josh> CLOSED: [2017-08-11 Fri 14:57] SCHEDULED: <2017-08-12 Sat
Josh> .+1d>
Josh> Where the task is marked as "DONE", and weirdly tags are added
Josh> in some of the startup config at the beginning of the file.
This may be related somehow to the problem mentioned in the thread
"Change in appearance of org-todo-keywords". It's good to have your
minimal example.
Best wishes.
--
--
Colin Baxter
m43cap@yandex.com
GnuPG fingerprint: 68A8 799C 0230 16E7 BF68 2A27 BBFA 2492 91F5 41C8
next prev parent reply other threads:[~2017-08-11 7:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-11 7:04 Bug: Marking repeated tasks with two tags as DONE causes problems Josh Moller-Mara
2017-08-11 7:27 ` Colin Baxter [this message]
2017-08-11 9:06 ` Nicolas Goaziou
2017-08-11 9:41 ` Josh Moller-Mara
2017-08-11 16:17 ` Colin Baxter
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=87tw1e36oq.fsf@yandex.com \
--to=m43cap@yandex.com \
--cc=emacs-orgmode@gnu.org \
--cc=jmm@cns.nyu.edu \
/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).