From: Sharon Kimble <boudiccas@skimble.plus.com>
To: Ian Barton <lists@wilkesley.net>
Cc: ian@manor-farm.org, org-mode <emacs-orgmode@gnu.org>
Subject: Re: crossing out tasks
Date: Thu, 08 May 2014 22:09:18 +0100 [thread overview]
Message-ID: <87zjisyo3l.fsf@skimble.plus.com> (raw)
In-Reply-To: <536B87A4.20203@wilkesley.net> (Ian Barton's message of "Thu, 08 May 2014 14:33:24 +0100")
[-- Attachment #1: Type: text/plain, Size: 1144 bytes --]
Ian Barton <lists@wilkesley.net> writes:
> On 08/05/14 11:12, Sharon Kimble wrote:
>> This is so simple but I can't find a solution. If I have a list of
>> tasks with + in front, when done I can put a + at the end which
>> crosses them out, making it very easy to see what I have left to
>> do. Except, sometimes the preceding task inherits the crossing out
>> too, even though it does not have a + at the end, so how can I stop
>> the inheritance please?
>>
>> Sharon.
>
> I seem to remember that Carsten doesn't like strike through
> faces. Maybe it's his secret plot to stop people using them:)
>
> On a more constructive note. Why don't you just make them TODO's and
> then mark them DONE in the usual way. You should be able to customize
> the DONE face to a strike through one.
>
I've just converted them from TODOS, and this task-list seemed a
simpler and easier idea, but I'll try check-boxes like Nick
suggested.
Sharon.
--
A taste of linux = http://www.sharons.org.uk
my git repo = https://bitbucket.org/boudiccas/dots
TGmeds = http://www.tgmeds.org.uk
Debian testing, Fluxbox 1.3.5, emacs 24.4.50.21
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2014-05-08 21:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-08 10:12 crossing out tasks Sharon Kimble
2014-05-08 13:33 ` Ian Barton
2014-05-08 13:43 ` Nick Dokos
2014-05-08 21:09 ` Sharon Kimble [this message]
2014-05-09 12:47 ` Bastien
2014-05-09 15:43 ` 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=87zjisyo3l.fsf@skimble.plus.com \
--to=boudiccas@skimble.plus.com \
--cc=emacs-orgmode@gnu.org \
--cc=ian@manor-farm.org \
--cc=lists@wilkesley.net \
/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).