From: John Kitchin <jkitchin@andrew.cmu.edu>
To: Rainer M Krug <r.m.krug@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: inline TODO?
Date: Fri, 14 Dec 2012 10:54:09 -0500 [thread overview]
Message-ID: <CAJ51ETrAFC_fRGQdQbrvnBZ-YgmLb48ZZ8Zi5b9o1_78CZ8ShA@mail.gmail.com> (raw)
In-Reply-To: <50CB456D.5090701@gmail.com>
That is exactly what I wanted! Thanks.
John
-----------------------------------
John Kitchin
Associate Professor
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
http://kitchingroup.cheme.cmu.edu
On Fri, Dec 14, 2012 at 10:27 AM, Rainer M Krug <r.m.krug@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 14/12/12 15:53, John Kitchin wrote:
>> Is there a way to have a TODO item in an org-file that is not in a headline and that shows up
>> in the agenda?
> Hi
>
> Look for inline tasks:
> http://stackoverflow.com/questions/11718401/how-to-use-todo-tags-in-org-mode-without-defining-
> headlines
>
> Does this help?
>
> Never used them, but always wanted to...
>
> Cheers,
>
> Rainer
>
>>
>> I have been using org-mode to write papers, and often in the middle of a section I want to make
>> a TODO item, right where something needs to be done, and I do not want to make a new heading
>> there as it changes the overall organization (even though it is temporary and will be removed).
>> Something like this would be great:
>>
>> #+TODO: finish this section DEADLINE: <2012-12-14 Fri>
>>
>>
>> At the moment I can search for these lines, but it would be nice if they showed up in the
>> agenda. Is there any way to do this that I am overlooking?
>>
>> Thanks,
>>
>> j
>>
>>
>> Here is a simple usage for example.
>>
>>
>> * introduction
>>
>> Lots of text. blah blah #+TODO: finish this section DEADLINE: <2012-12-14 Fri>
>>
>> end of introductory text that is still in the introduction section.
>>
>> * Methods yadayadaya.
>>
>> ** TODO I do not like this because subsequent text is in a subsection
>>
>> we used this method to do that.
>>
>> * Conclusions The end.
>>
>> John
>>
>> ----------------------------------- John Kitchin Associate Professor Doherty Hall A207F
>> Department of Chemical Engineering Carnegie Mellon University Pittsburgh, PA 15213
>> 412-268-7803 http://kitchingroup.cheme.cmu.edu
>>
>>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.11 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iEYEARECAAYFAlDLRW0ACgkQoYgNqgF2egq3zgCfUH2ZKnpcoJ9BQOv4TpzGNMNQ
> QhwAn2wALy9ARN7Iwb4Mw1/zcqkEsMLZ
> =8JN0
> -----END PGP SIGNATURE-----
next prev parent reply other threads:[~2012-12-14 15:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-14 14:53 inline TODO? John Kitchin
2012-12-14 15:27 ` Rainer M Krug
2012-12-14 15:54 ` John Kitchin [this message]
2012-12-16 5:57 ` J. David Boyd
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=CAJ51ETrAFC_fRGQdQbrvnBZ-YgmLb48ZZ8Zi5b9o1_78CZ8ShA@mail.gmail.com \
--to=jkitchin@andrew.cmu.edu \
--cc=emacs-orgmode@gnu.org \
--cc=r.m.krug@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 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).