From: Myles English <mylesenglish@gmail.com>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: Emacs-orgmode <Emacs-orgmode@gnu.org>
Subject: Re: clocking into an inline task before any headings
Date: Fri, 30 Aug 2013 12:20:03 +0100 [thread overview]
Message-ID: <87wqn3o270.fsf@gmail.com> (raw)
In-Reply-To: <5EEF3962-E89F-4BBA-AB47-C5525A9C964D@gmail.com>
Hi Carsten,
Carsten Dominik writes:
> On 14.8.2013, at 16:36, Myles English <mylesenglish@gmail.com> wrote:
>
>> Are inline tasks allowed to be used before any other headings? (I hope
>> they are.)
>
> No, they are not.
>
> Why don't you just make it a normal headline?
Okay, I can put the inline task under a normal headline with a
:noheading: tag that causes a filter to omit the headline itself, and
this is good enough for my needs:
* Like This :noheading:
*************** TODO Something inline
*************** END
Just to explain what I am doing though: writing a report, e.g.:
* Introduction
* Method
* Conclusions
Adding tasks as headings breaks up the structure undesirably:
* TODO Decide on a layout for the whole document
* Introduction
* TODO Finish writing the introduction
* Method
* Conclusions
Alternatively, using inline tasks, the document structure is still easy
to see (scanning down the left side) and they fold nicely:
*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
* Conclusions
Labouring the point at bit, I see the headlines as the fingers on my
left hand and the inline tasks are the fingers on my right hand and they
interleave:
*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
** Setup
*** Safety
*************** TODO Add fire exits...
**** Insurance
*************** TODO Ring broker...
* Conclusions
Changing the inline task before the Introduction to be under a headline
works but breaks up the document a little at the start:
* First task :noheading:
*************** TODO Decide on a layout for the whole document...
* Introduction
*************** TODO Finish writing the introduction...
* Method
** Setup
*** Safety
*************** TODO Add fire exits...
**** Insurance
*************** TODO Ring broker...
* Conclusions
(Another issue that may be related to this is that the preamble in a
complicated document for LaTeX export takes up a whole screen and it
would be nice to be able to fold it.)
Thanks,
Myles
prev parent reply other threads:[~2013-08-30 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 14:36 clocking into an inline task before any headings Myles English
2013-08-23 9:56 ` Carsten Dominik
2013-08-30 11:20 ` Myles English [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wqn3o270.fsf@gmail.com \
--to=mylesenglish@gmail.com \
--cc=Emacs-orgmode@gnu.org \
--cc=carsten.dominik@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.