From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: Where to keep draft work?
Date: Tue, 26 May 2015 09:08:44 -0400 [thread overview]
Message-ID: <87y4kba3kz.fsf@ericabrahamsen.net> (raw)
In-Reply-To: loom.20150526T100507-590@post.gmane.org
SabreWolfy <sabrewolfy@gmail.com> writes:
> Consider the following Org file, which is used to generate an Agenda:
>
> * Write the big report
> DEADLINE: <2015-05-26 Tue 12:00>
> * Write the small report
> DEADLINE: <2015-06-02 Tue 12:00>
> * Plan the draft proposal
> SCHEDULED: <2015-05-28 Thu 09:00>
>
> Where is the best place to store the actual text of the reports and
> proposals? Should it be stored under each heading? Or in a drawer? Or linked?
>
> I call the Agenda and see entries for the day, and then scroll to one and
> press <Tab> to jump to it. This would be a good place to store the text?
I almost always end up putting the text directly under the headline, and
then doing a subtree export. As John notes, though, if you've got a
particularly complex document it might feel cleaned to put it in a
separate file. On the other hand, I suspect there's nothing you can do
with a separate file that you can't do with subtree properties/export
options.
From the point of view of reaching the text from the Agenda, I doubt
there's much difference -- just the matter of an extra RET if you are
following a link to a separate file.
Eric
prev parent reply other threads:[~2015-05-26 13:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-26 8:12 Where to keep draft work? SabreWolfy
2015-05-26 9:25 ` John Kitchin
2015-05-26 13:08 ` Eric Abrahamsen [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
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=87y4kba3kz.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).