Rens Oliemans writes:
> I hear the same sentiment throughout this thread by Ihor and Bob, that it's
> undesirable to have many TODO items that just lay around for a long time.
IMHO, the most critical is not having many todo items *in agenda* -
staying in front of you every day and pressing on to
Hi Rens,
Rens Oliemans writes:
> Thank you for sharing this! It seems like reducing the amount of loose TODO
> tasks is an important part:
>
>> * Every week I check the TODO and WAIT tasks that do not appear in my
>> calendar.
Indeed. In general, the agenda views that I use routinely nudge me t
Bastien Guerry writes:
> I've finally found some time to describe my Org workflow:
> https://bzg.fr/en/the-zen-of-task-management-with-org/
Thank you for sharing this! It seems like reducing the amount of loose TODO
tasks is an important part:
> * Every week I check the TODO
"Bob Newell" writes:
>> That's a terrible terrible idea to pollute agenda view with tasks that
>> do not absolutely need to be done on a given day. Such agenda is useless
>> in the long run.
>
> A terrific insight. While I think I mostly use orgmode effectively this is a
> mistake I'm clearly m
On Sun, Apr 20, 2025, at 08:20, Ihor Radchenko wrote:
> That's a terrible terrible idea to pollute agenda view with tasks that
> do not absolutely need to be done on a given day. Such agenda is useless
> in the long run.
A terrific insight. While I think I mostly use orgmode effectively this
Günter Lichtenberg writes:
> I also have a lot of projects that are shifting and changing and regularly
> something
> unscheduled pops up. Maybe a bit obvious, but what helped me most was to set
> aside time
> every week on Friday (as org habit "Plan Next Week") to (re)organise tasks
> for
On Sunday, 20 April 2025 19:50:43 CEST Ihor Radchenko wrote:
> Bastien Guerry writes:
> > I've finally found some time to describe my Org workflow:
> > https://bzg.fr/en/the-zen-of-task-management-with-org/
> > ...
> > And I'm curious to see how it compares
Ihor Radchenko writes:
> In my setup, TODO implies "here is a task, I should likely be done, but
> I still need to figure out the details".
Yes... as Rudolf suggested, I will try "PLAN" for this.
--
Bastien
Rudolf Adamkovič writes:
> Idea: Perhaps the default TODO keyword could mean "next" and the
> "inventory" tasks could use a new keyword, like IDLE, PLAN, or L8TR.
Good idea! I switched to using ONGO/TODO/PLAN as you suggest, and I
updated the blog post. Thanks!
--
Bastien
Rudolf Adamkovič writes:
> Idea: Perhaps the default TODO keyword could mean "next" and the
> "inventory" tasks could use a new keyword, like IDLE, PLAN, or L8TR.
> That way, one does not hide items from the agenda by mistake.
Depends. TODO is kind of the default.
In my setup, TODO implies "here
Bastien Guerry writes:
> I guess you draw a similar line between ONGO and other keywords, with
> "ONGO" having a similar meaning to "activated" for me.
Good point! Both next and ongoing parameterize the task along the same
axis. I will stop using priorities, then. Thank you for taking the
tim
Rudolf Adamkovič writes:
> Here are some more details from my setup. :)
Interesting, thanks!
> I used to use NEXT but since realized:
>
> NEXT is a priority, not a state.
To me, "NEXT" does not mean that the task is more important or urgent
than TODO tasks, it means that the task is in the "
Bastien Guerry writes:
> - STRT tasks do not change often: they are either STRT or DONE (hence
> the need for dedicated agenda views).
>
> - What *I* change a lot are (1) priority cookies and (2) NEXT/TODO
> status. Something that was NEXT suddenly becomes something I can
> forget, and vice
Ihor Radchenko writes:
> Fair enough. I tend to have dozens of projects that have to be running
> in parallel and prioritized depending on deadlines or new information
> arriving. So, I personally need an elaborate setup of project priorities
> and statuses. So, I use todo keywords on projects ju
Bastien Guerry writes:
> Ihor Radchenko writes:
>
>> Do you ever need to juggle large number of work projects with shifting
>> priorities and pauses?
>
> I don't really have "work projects", I just have a top level project
> called "work" that contains 2nd level tasks. I could have multiple work
Ihor Radchenko writes:
> Do you ever need to juggle large number of work projects with shifting
> priorities and pauses?
I don't really have "work projects", I just have a top level project
called "work" that contains 2nd level tasks. I could have multiple work
projects, but I don't have that ne
Bastien Guerry writes:
> I've finally found some time to describe my Org workflow:
> https://bzg.fr/en/the-zen-of-task-management-with-org/
> ...
> And I'm curious to see how it compares to other workflows.
Do you ever need to juggle large number of work projects with s
Bastien Guerry writes:
> And I'm curious to see how it compares to other workflows.
My keywords are similar to yours, but slightly more readable:
- ONGO instead of STRT
- SKIP instead of CANX
:)
Rudy
--
"Logic is a science of the necessary laws of thought, without which no
employment of the
Hi Russell,
Russell Adams writes:
> In comparison, I often use a file per project and I focus more on TODO
> trees than scheduled items. I do maintain a few standard files that I
> only update via "remember", and access via agenda.
Thanks for sharing.
> Everyone finds their own workflow.
Yes,
Rudolf Adamkovič writes:
> My keywords are similar to yours, but slightly more readable:
>
> - ONGO instead of STRT
> - SKIP instead of CANX
Very nice! Adopted, thanks :)
--
Bastien
On Thu, Apr 17, 2025 at 02:19:08PM +0200, Bastien Guerry wrote:
> I've finally found some time to describe my Org workflow:
> https://bzg.fr/en/the-zen-of-task-management-with-org/
>
> I don't use comments on my blog, feel free to discuss it here:
> https://news.ycombin
I've finally found some time to describe my Org workflow:
https://bzg.fr/en/the-zen-of-task-management-with-org/
I don't use comments on my blog, feel free to discuss it here:
https://news.ycombinator.com/item?id=43715714
I hope this will be useful!
And I'm curious to see how
22 matches
Mail list logo
