From: "David Thole" <dthole@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Workflow Ideas/questions
Date: Tue, 24 Mar 2009 15:51:00 -0500 (CDT) [thread overview]
Message-ID: <278452667f8c27630c57917c33690e13.squirrel@mail.thedarktrumpet.com> (raw)
Hey all,
I was thinking a bit about my workflow with org-mode, and I'm thinking
that I should change up a bit of how I'm doing stuff. Basically what I do
now is use org-mode for my GTD stuff (that is, ticket management, notes
about tickets, etc), and then use muse mode for other stuff.
Right now my structure is:
ris.org = my tickets specific to work
work.org = my work tasks that aren't tickets
home.org = my home tasks
The problem I have now is that I use muse-mode for project notes, which
can be on multiple machines sometimes. So the agenda itself loads those
three org files to display the ris/work/home tasks, and I use follow mode
and add a few notes here and there to the tickets, (ris.org files that
is).
So really my curious workflow questions are:
* Ticket information - SQL statement, code, etc..that can get pretty
verbose. Is a drawer OK for that? How do others handle that information
* Meeting notes - would another org file be useful for that? If I want to
publish the file into something that could have a TOC and all that...I
don't know how to explain this better, I kinda want something to be able
to view this through a browser sometimes. *shrug* some ideas on this
would be helpful
* Organization - Could I organize things more efficiently? Thinking of
maybe using properties drawer a bit more.
General ideas would be appreciative. Thanks for the help.
-David
next reply other threads:[~2009-03-24 20:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 20:51 David Thole [this message]
2009-03-25 21:18 ` Workflow Ideas/questions Manish
2009-03-26 2:42 ` Peter Jones
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=278452667f8c27630c57917c33690e13.squirrel@mail.thedarktrumpet.com \
--to=dthole@gmail.com \
--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).