From: Greg Newman <gregoryjnewman@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Re: How you ORGanize yourself? (aka: Why not one file to rule'em all?)
Date: Tue, 20 Apr 2010 19:16:30 -0400 [thread overview]
Message-ID: <u2t71454fac1004201616i3784623dq8729875ceab19d66@mail.gmail.com> (raw)
In-Reply-To: <op.vbg8hgxm6smz6p@laptop-casa.lan>
[-- Attachment #1.1: Type: text/plain, Size: 1618 bytes --]
My process has gone through some revisions. My current setup is as follows:
client-projects.org
I keep all paid projects for clients in one big file. I used to keep them
in a file for each client until one of them noticed that their name was
being pushed to github in my agenda files.
studio-projects.org
This file holds all internal projects for my studio. Paintings, drawings,
administrative tasks, repair and studio related research materials.
home-projects.org
Just that. Anything related to the house, cars, wife, kid, dogs, etc.
notes.org
I use this file for random thoughts and information I find online.
mind.org
How to explain this one? When I find information that I want to act on in
the future as R&D I throw it into mind.org and
give it a todo status. Usually stuff in here pertains to things I don't
understand and want to spend time learning. Hence the name.
phone.org
When on client calls I take notes in the phone file which later gets refiled
to their respective places
calendar.org
This is synced using Doug Hellmann's ical2org python script. I have a cron
set to sync it every hour so
that my google calendar updates my org file. I have todochiku installed to
notify me via growl of appointments.
I may go back to having a single org file for each client. Right now I have
about 20 projects in that file with long lists and
I'm struggling a little with keeping it organized enough that I don't lose
track of projects.
Beyond this setup, every hour a cron syncs my org files to a private
mercurial repository at bitbucket.
— Greg
[-- Attachment #1.2: Type: text/html, Size: 2393 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-04-20 23:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 5:41 How you ORGanize yourself? (aka: Why not one file to rule'em all?) Marcelo de Moraes Serpa
2010-04-16 12:43 ` tycho garen
2010-04-17 13:50 ` Matt Lundin
2010-04-17 20:54 ` Carsten Dominik
2010-04-18 6:35 ` Marcelo de Moraes Serpa
2010-04-18 6:51 ` Marcelo de Moraes Serpa
2010-04-19 15:07 ` Matthew Lundin
2010-04-19 16:08 ` Carsten Dominik
2010-04-20 12:02 ` Matthew Lundin
2010-04-20 19:59 ` Flavio Souza
2010-04-20 23:16 ` Greg Newman [this message]
2010-04-21 9:51 ` Alan E. Davis
2010-04-21 11:38 ` Tim O'Callaghan
2010-04-21 12:52 ` Bernt Hansen
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=u2t71454fac1004201616i3784623dq8729875ceab19d66@mail.gmail.com \
--to=gregoryjnewman@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).