emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Ali Tofigh <alix.tofigh@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Suggestions needed for handling "ideas"
Date: Mon, 12 Apr 2010 15:38:23 -0500	[thread overview]
Message-ID: <t2qa037f7361004121338wbfe9e654q5c2a3e75e55abfa3@mail.gmail.com> (raw)
In-Reply-To: <n2zc8f5e1e41004121246jaca01d34y604ed18ba1de1962@mail.gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 3590 bytes --]

On Mon, Apr 12, 2010 at 2:46 PM, Ali Tofigh <alix.tofigh@gmail.com> wrote:

> Hello everyone,
>
> I'm a new user of org-mode, and seeing the great potential, I am
> trying to switch to org-mode for handling my day-to-day tasks. I'm
> going to start off by using org-mode to handle my projects and I need
> some advice.
>
>
I'm new to this as well and started in a very similar way:
- begin with just notes
- ramp up to todo tracking
- continue to ramp up to scheduling/full-fledged work data capture system


> I like to keep my projects self-contained. Therefore I use one
> org-file for each project. Each org-file contains two main headlines:
> journal and tasks. Under journal I collect all kinds of information:
> meeting notes, relevant stuff I've read, urls, etc. I also write down
> what I have done every few days. The journal entries are sorted
> chornologically. Under tasks I keep all todo items.
>
>
I started with separate, then went to all-in-one file, and think I'm going
back to one-per, mainly because of issues with being too deep in an outline
already by having one file; in other words, I blow a headline with project
name, then another with either 'journals' or 'todos', etc., and only then am
I in day-to-day notes...

Anyway, your setup sounds similar to what I'm leaning toward as well.


> Frequently my notes on meetings contain ideas for stuff to try. Does
> anyone have any advice on how to handle these?
>
>
I'm very 'idea' centered as well. See some 'ideas' below :)


> I don't want to keep them as todo items in the journal since I like to
> keep changing the todos (e.g., dividing them into subtasks) and I
> don't want those changes to appear in the journal.


I agree with this -- my idea for a 'journal' is a record of my work, meeting
notes, etc. Ideas are usually equivalent to 'off-topic concept to try later
that came up in the context of this meeting but that will develop
separately.'


> My initial thought
> was to create one headline for each idea and tag it with ":idea:". I
> could then easily go through all ideas in a project and choose the
> ones I want to work on by creating todo items. Those ideas would then
> be further tagged with ":handled:" or something similar. This way I
> could search for unhandled ideas in my projects. As an alternative I
> could use separate todo keywords for todos and ideas.
>

What about:

### IDEA 1 ###
--- file: project_name.org ---
* Journals
** Title <date>
Notes about stuff

* Ideas
** TODO idea 1 <date>
** WORKING idea 2
** DONE idea 3 <date>

Something like this? This could track ideas in each project and if you do
use them as TODOs you can pull them up with agenda to check ideas across all
projects.

### IDEA 2 ###
- a remember template for ideas?
- file keystrokes set to set the file to a particular project's file with a
simple key entry?
- or... one file called 'ideas.org' divided by projects (or just tag idea
headlines with the project name)
--- then use remember-mode to add ideas to that file when you're in
meetings/taking notes in a different, dedicated project file?


> Any specific advice or just general thoughts are most appreciated.
>
>
I'm so new I can hardly believe I'm proposing these ideas as I don't even
know that I know everything necessary to implement them! But... these are
things i ponder so I thought I'd share...


> Cheers,
> /Ali
>
>
John


>
> _______________________________________________
> 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
>

[-- Attachment #1.2: Type: text/html, Size: 5515 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

  reply	other threads:[~2010-04-12 20:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-12 19:46 Suggestions needed for handling "ideas" Ali Tofigh
2010-04-12 20:38 ` John Hendy [this message]
2010-04-12 21:04   ` Ali Tofigh
2010-04-25  7:46 ` John Wiegley
2010-04-26 14:47   ` Ali Tofigh
2010-04-26 17:00     ` Matt Lundin
2010-04-26 17:30       ` Ali Tofigh
2010-05-20  0:14       ` Ali Tofigh
2010-04-27 10:07     ` Sébastien Vauban
2010-04-28  1:59       ` Bernt Hansen
2010-04-26 16:16   ` Nathan Neff

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=t2qa037f7361004121338wbfe9e654q5c2a3e75e55abfa3@mail.gmail.com \
    --to=jw.hendy@gmail.com \
    --cc=alix.tofigh@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).