emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: c.buhtz@posteo.jp
Cc: Emacs-orgmode@gnu.org
Subject: Re: Use-case: simple nodes and todo-list
Date: Fri, 09 Oct 2020 13:53:37 +0100	[thread overview]
Message-ID: <87d01rlfvy.fsf@ucl.ac.uk> (raw)
In-Reply-To: <e4e68cd84a3043ed900a38729fe27e72@posteo.de> (c. buhtz's message of "Fri, 09 Oct 2020 10:17:56 +0200")

My use of org actually quite closely manages your paper based
approach.  I have 3 main org files that cover the tasks you have

1. todo.org which has all my todo items.  every now and again, I go
   through this list and schedule some of them.  I do put deadlines on
   items if they have hard deadlines (i.e. of the type that says "this
   *has* to be done by then or else...") but I do not create artificial

2. notes.org that is simple a collection of (a large number of)
   snippets, each in a single top level headline.  These are all tagged
   when created with as many tags per entry as I can think of at the
   time.  I can then usually find what I want very quickly through the
   tag search functionality in org-agenda (C-c a m TAG RET) with
   org-agenda bound to "C-c a".  But see below.

3. diary.org for appointments and meetings.  This is the file that sees
   the most activity but only because I seem to live in meetings these

The key with the first two is to not worry about how you structure
information.  If all else fails, you can use the full power of Emacs to
find things (occur; isearch-forward-regexp; etc.).  


: Eric S Fraga via Emacs 28.0.50, Org release_9.4-38-g16f505

      parent reply	other threads:[~2020-10-09 12:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09  8:17 Use-case: simple nodes and todo-list c.buhtz
2020-10-09  8:37 ` Robert Pluim
2020-10-09  9:30 ` Joost Kremers
2020-10-09 12:53 ` Eric S Fraga [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:

  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=87d01rlfvy.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --cc=Emacs-orgmode@gnu.org \
    --cc=c.buhtz@posteo.jp \


* 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


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).