emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: daniela-spit@gmx.it, emacs-orgmode@gnu.org,
	Jean Louis <bugs@gnu.support>
Subject: Re: Adding Org Files to org-agenda-files
Date: Mon, 30 Nov 2020 00:00:30 +1100	[thread overview]
Message-ID: <87360sz5ap.fsf@gmail.com> (raw)
In-Reply-To: <87ft4s5oug.fsf@localhost>


Ihor Radchenko <yantar92@gmail.com> writes:

> Jean Louis <bugs@gnu.support> writes:
>
>> Currently I am researching "NEXT" and how people are thinking and
>> trying to see if I miss some concepts. My approach seem to be
>> simpler. There is project and there are tasks in their most logical
>> chronological or executable order just as a program. One has to do
>> first one, then next. Which one is next is clear from the order of
>> tasks. Marking it "NEXT" to me seem redundant as it would mean I have
>> not made good order.
>
> NEXT is relevant to complex projects where multiple tasks can be active
> at the same time. Or when some urgent tasks are added to the project as
> it goes. Then, instead of constant reshuffling of the task order and
> re-evaluating the order of tasks, one can simply mark the new urgent
> tasks NEXT and later use sparse trees to only look at the tasks that
> should be done at the current stage of the project. The key point is
> minimising exposure to irrelevant information - the number of tasks in
> large project can be demoralising, especially if one gets reminded about
> it frequently.
>
> You might also check
> https://old.reddit.com/r/orgmode/comments/i4hx1z/gtd_problem_with_todo_workflowconstantly/g0ihg2d/
>

Exactly. Not all the tasks in my task list are related or have
dependencies between them. I use NEXT as part of my planning process.

>> If the type of heading is "task" then I do not need to use "TODO" as
>> it implies it is task. But Org headings do not have fixed types so it
>> is visually and practically better to use TODO. Here would the
>> inheritance be useful more than to tags. As if user marks one heading
>> as TODO, then all subtrees could automatically get its TODO.
>

This assumes the only things you have under a TODO heading is other TODO
headings. That isn't how I structure my work. I might have many other
headings under a TODO heading which are not tasks, but are perhaps
related to the task. Sometimes I might have many tasks which are not
dependent on each other and so are all at the same level.

> That can be done. Should be trivial using org-edna
> (http://www.nongnu.org/org-edna-el/), for example. Or you can use
> org-trigger-hook and mark all the children with TODO keyword if the
> parent heading is marked TODO.
>

>> The DELEGATED type, I have seen people using this and myself also. But
>> if something is fully delegated and not any more mine, then I would
>> not have it in my file. So it is something usually that I have to
>> think of. Many of the tasks I think of are already assigned, I could
>> call it delegated. And I keep property :ASSIGNED: under the Org
>> heading. When I wish to send this task, I press one key and it is
>> automatically sent to the person assigned. But I am one supervising it.
>
> I guess the key reason to have DELEGATED is just to be reminded to
> followup on the progress.
>

Exactly. I don't just assign a task to someone and then forget about it.
I want to be reminded about which tasks have been delegated so that I
can follow up on them. Sometimes a delegated task is a dependency in
tasks which I have to do. I need to know when it is done in order to do
my task etc.

>> By using this approach one can assign tasks:
>>
>> #+TITLE: My Org File
>> #+AUTHOR: Me
>> #+PROPERTY: ASSIGNED_ALL James Jane John Juda Mehdi
>>
>> ** TODO Negotiate with land owner
>>
>> Now when one does {C-c C-x p} the minibuffer prompt asks for
>> "Property: " and there is ASSIGNED available as one of choices.
>>
>> In the next step it asks user for ASSIGNED value, and there are
>> choices such as James Jane John Juda and Mehdi. Then it becomes like
>> this.
>>
>> ** TODO Negotiate with land owner
>>    :PROPERTIES:
>>    :ASSIGNED: Mehdi
>>    :END:
>>
>> This way the major type TODO does not change, but one knows that it is
>> assigned or delegated to Mehdi.
>
> I would do it in an opposite manner - mark the task DELEGATED, which
> triggers {C-c C-x p} and prompts me for the ASSIGNED value. The
> advantage of my method is simply that it is easier to see later -
> DELEGATED keyword is visible on the headline, which the PROPERTY drawer
> is folded by default. Of course, it would not matter if you configure
> org to not fold the PROPERTY drawers.
>

nd this highlights the main benefit of org mode. There is no 'one right
way'. It is up to the user to decide how to best use it to meet their
requirements. For me, I want a text only, relatively simple system which
has minimal dependencies on anything else (such as a database). I want
to be able to copy all my org files onto a thumb drive or put them into
the cloud and know I can access/use them from anywhere where I can run
Emacs or if Emacs is unavailable, just a basic editor where I can
edit/update them as text.

--
Tim Cross


  reply	other threads:[~2020-11-29 13:03 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 15:39 Adding Org Files to org-agenda-files daniela-spit
2020-11-28 16:51 ` Jeremie Juste
2020-11-28 16:54   ` daniela-spit
2020-11-28 17:01   ` daniela-spit
2020-11-28 17:41     ` Jeremie Juste
2020-11-28 18:12       ` daniela-spit
2020-11-28 18:30       ` daniela-spit
2020-11-28 18:43       ` daniela-spit
2020-11-28 19:01         ` Jeremie Juste
2020-11-28 19:16           ` daniela-spit
2020-11-28 19:26             ` Detlef Steuer
2020-11-28 19:44               ` daniela-spit
2020-11-28 19:55             ` Jeremie Juste
2020-11-28 20:06               ` daniela-spit
2020-11-28 20:11               ` daniela-spit
2020-11-28 20:27                 ` Jeremie Juste
2020-11-28 20:40                   ` daniela-spit
2020-11-28 21:32                     ` Jeremie Juste
2020-11-28 21:45                       ` daniela-spit
2020-11-28 23:18                         ` Jeremie Juste
2020-11-28 23:29                           ` daniela-spit
2020-11-29  1:36                             ` Tim Cross
2020-11-29  2:54                               ` daniela-spit
2020-11-29  3:51                                 ` Tim Cross
2020-11-29  4:05                                   ` daniela-spit
2020-11-29  5:23                                     ` Tim Cross
2020-11-29  9:30                                       ` Jean Louis
2020-11-29  6:50                                     ` Jean Louis
2020-11-29  6:41                                   ` Jean Louis
2020-11-29 12:28                                     ` Ihor Radchenko
2020-11-29 13:00                                       ` Tim Cross [this message]
2020-11-29 17:11                                         ` Jean Louis
2020-11-29 17:05                                       ` Jean Louis
2020-12-01  2:24                                         ` Ihor Radchenko
2020-12-01  8:59                                           ` Jean Louis
2020-12-13 15:36                                             ` Ihor Radchenko
2020-12-13 16:27                                               ` steve-humphreys
2020-12-25  2:17                                                 ` Ihor Radchenko
2020-12-13 20:21                                               ` Jean Louis
2020-12-13 20:59                                               ` Tim Cross
2020-12-13 21:59                                                 ` pietru
2020-12-13 23:28                                                 ` Jean Louis
2020-11-29  4:46                             ` Jean Louis
2020-11-29 14:46                               ` daniela-spit
2020-11-29 17:01                                 ` Tim Cross
2020-11-29 17:38                                   ` daniela-spit
2020-11-29 20:55                                     ` Jeremie Juste
2020-11-30  0:21                                       ` Tim Cross
2020-11-28 23:36                           ` daniela-spit
2020-11-29  5:51                             ` Jean Louis
2020-11-28 20:28                 ` daniela-spit
2020-11-28 18:50       ` daniela-spit

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=87360sz5ap.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=bugs@gnu.support \
    --cc=daniela-spit@gmx.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@gmail.com \
    /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).