From: Robert Pluim <firstname.lastname@example.org>
Subject: Re: Use-case: simple nodes and todo-list
Date: Fri, 09 Oct 2020 10:37:40 +0200 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <firstname.lastname@example.org> (c. buhtz's message of "Fri, 09 Oct 2020 10:17:56 +0200")
>>>>> On Fri, 09 Oct 2020 10:17:56 +0200, email@example.com said:
c> I still read something about org-mode.
c> It is a complex and powerfull tool. I now try fit/transform my current
c> workflow and use-cases to org-mode. So maybe you can give me a simple
c> yes-now if this could be fullfilled with org-mode.
c> 1. Simple notes with keywords and endless time to life
Yes. org *allows* you to invent a complex deadline/scheduling
workflow, but at its most basic you just write:
* Project 1 :work:
** Task 1
** Task 2
* Project 2 :play:
and just stick your notes in there (you can do things with lists,
checkboxes, etc, but Iʼd start simple).
c> I have notes (most of them as post-its on the wall and monitor in my
c> office) with information's I am not able or willing to remember. But I
c> need this information's every few days. e.g. numbers for bank-account,
c> projects, persons
c> I find this information's by place (post-it glued to a specific place
c> in my office). When they are digitized I would use keywords or in-text
c> search. e.g. searching for the project name "my project" to find its
Everyone has their own system, but I put "stuff I donʼt need often" in
one org file, then I have a 'work' file and a 'play' file. Ordinary
emacs search commands are enough, but again org has support for
searching by tags, name etc.
c> 2.ToDo List without time information's
c> Currently I use a one-page-paper handwritten as a ToDo List. I
c> re-create it every week. It helps me. I make priorities with some
c> colors or underlines. And it (maybe) makes my workload visible to my
c> leaders when sitting in a meeting and having the ToDo list on the
c> table. ;)
c> In the past I also tried "taskwarrior". Very powerfull, I loved
c> it. But it did not fit to my workflow. I know this is apocalyptic and
c> hard to imagine but deadlines are useless in my workflow. :D So
c> taskwarrior did not helped be it just build up more pressure to
c> me. Simple explanation: My work is influenced by to much unknown
c> external spontaneous factors. It is useless to make
c> plans/deadlines. Yes it is horror, I work on it. But I am not on that
c> level of the hierarchy to make the fundamental needed changes.
* TODO get milk :housekeeping:
* TODO feed cat :housekeeping:pets:
(and the 'housekeeping' stuff is also completely optional).
For priorities org has support for 3 levels of priority built in, so
* TODO [#B] get milk :housekeeping:
* TODO [#A] feed cat :housekeeping:pets:
There are convenient key bindings for setting the priorites on items.
For what you've described, Iʼd start by reading (info "(org) TODO
Items"), and stopping when you've reached the level you want to use.
next prev parent reply other threads:[~2020-10-09 8:40 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 [this message]
2020-10-09 9:30 ` Joost Kremers
2020-10-09 12:53 ` Eric S Fraga
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 \
* 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).