From: Sharon Kimble <boudiccas@skimble.plus.com>
To: org-mode-email <emacs-orgmode@gnu.org>
Subject: subtasks causing greying of entry in agenda
Date: Wed, 31 Aug 2016 06:06:41 +0100 [thread overview]
Message-ID: <87zintbk7y.fsf@skimble.plus.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1138 bytes --]
I've discovered something this morning that puzzles me, and I can't work out how to google it!
In my organiser file I have this task set up -
--8<---------------cut here---------------start------------->8---
*** TODO end of life care
DEADLINE: <2016-12-30 Fri> SCHEDULED: <2016-08-31 Wed +1d>
:PROPERTIES:
:35:00: 35:00
:BUDGET_WEEK: 35:00
:BUDGET_MONTH: 140:00
:BUDGET_YEAR: 500:00
:Effort: 500:00
:END:
:LOGBOOK:
CLOCK: [2016-08-31 Wed 02:46]--[2016-08-31 Wed 03:47] => 1:01
CLOCK: [2016-08-31 Wed 02:22]--[2016-08-31 Wed 02:23] => 0:01
:END:
**** TODO death.org
**** TODO to include 'caring with dignity'
--8<---------------cut here---------------end--------------->8---
And when its displayed in the agenda it shows as a grey line of text
which is different from other surrounding text, see attached screenshot
snippet [fn:1].
However, if I take the subtasks out it displays perfectly normally. So
how can I have it displaying normally but still retain the subtasks
please? Are the subtasks position-dependent? Although in my experiments
they don't seem to be.
Thanks
Sharon.
[fn:1]
[-- Attachment #1.2: Screenshot-2016-08-31-05:50:46.png --]
[-- Type: image/png, Size: 7683 bytes --]
[-- Attachment #1.3: Type: text/plain, Size: 129 bytes --]
--
A taste of linux = http://www.sharons.org.uk
TGmeds = http://www.tgmeds.org.uk
Debian 8.4, fluxbox 1.3.7, emacs 25.1.1
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next reply other threads:[~2016-08-31 5:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 5:06 Sharon Kimble [this message]
2016-09-01 16:54 ` subtasks causing greying of entry in agenda Nicolas Goaziou
2016-09-01 20:36 ` Sharon Kimble
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=87zintbk7y.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=emacs-orgmode@gnu.org \
/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).