From: Matt Lundin <mdl@imapmail.org>
To: Xavier Maillard <xma@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: TODO keywords into drawers ?
Date: Tue, 18 Aug 2009 08:40:08 -0400 [thread overview]
Message-ID: <m23a7pb8if.fsf@fastmail.fm> (raw)
In-Reply-To: <874os5elig.wl%xma@gnu.org> (Xavier Maillard's message of "Tue, 18 Aug 2009 07:31:03 +0200")
Xavier Maillard <xma@gnu.org> writes:
> I extensively use remember to jot down new tasks/notes/... it
> feets perfectly since it is almost instantaneous.
>
> Sometimes, when at work, someone enters my room to speak about a
> project. When finished, I fire remember and try to sum up our
> discussion. This is not really a task to do but when reviewing my
> notes, it can be switched to a task entry.
>
> With my current setup, I have to differenciate, when in remember,
> if it is a task, a note or something else. If I do not, I do not
> see these entries when reviewing my org files. This is the big
> hole in my system which makes me not trust my system :/
As Carsten suggested, tags are probably the best way to mark tasks in
the way you suggest. Org-remember can be instructed (via templates) to
prompt for tags:
,----
| %^g prompt for tags, with completion on tags in target file.
| %^G prompt for tags, with completion all tags in all agenda files.
`----
Or, if you prefer, you could create different templates for different
tags (:NOTE:, :UNKNOWN:, etc.).
Another recommendation would be to instruct remember to file new notes
to a single location (e.g., inbox.org or * inbox). You could then
regularly review/process/empty this "inbox." That way you'd be sure not
to miss any new notes.
> What I'd like to have in orgmode is a simpler and homogeneous way
> to do things.
>
> * TODO foo bar
>
> would be
>
> * foo bar
> :TYPE:
> TODO
> :END:
>
> a note would be
>
> * foo bar
> :TYPE:
> NOTE
> :END:
>
> etc.
>
> A default entry would have a special entry type -say UNKNOWN-
> thus making the review much more trustable. What I like in this
> idea is the homegenous view of any orgmode file and I guess this
> would make orgmode file parsing a lot easier.
>
> We could even go further by storing all orgmode entries meta-data
> into drawers (tags, timestamps, states, ...)
If you want to avoid todos and tags, you can always use PROPERTY drawers
for custom metadata.
E.g.
* foo bar
:PROPERTIES:
:TYPE: note
:END:
And, of course, you can have remember templates prompt you to fill these
in.
,----
| %^{prop}p Prompt the user for a value for property prop
`----
Warning: it can be much slower to search for properties than to search
for todo-states and tags.
Best,
Matt
next prev parent reply other threads:[~2009-08-18 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 5:31 TODO keywords into drawers ? Xavier Maillard
2009-08-18 11:12 ` Carsten Dominik
2009-08-18 12:40 ` Matt Lundin [this message]
2009-08-18 19:00 ` Xavier Maillard
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=m23a7pb8if.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--cc=emacs-orgmode@gnu.org \
--cc=xma@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).