Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options

[Jean Louis]

* Ihor Radchenko <yantar92@gmail.com> [2020-12-14 15:46]:
> Jean Louis <bugs@gnu.support> writes:
> > Do you mean this:
> >
> > ** DONE Objective
> >    CLOSED: [2020-12-13 Sun 20:00]
> > *** TODO [#B] Step to do 1
> > *** TODO Step to do 2
> >
> > when org-enforce-todo-dependencies is true I can still say DONE for
> > Objective above. I have mentioned it today already. Maybe it works on
> > your side, it does not work here. Do I do something wrong? I am on
> > development Emacs version and it does not enforce under emacs -Q
...
> I just looked into this more. Most likely you were trying to set this
> variable manually. To take effect, this variable should be set using
> customisation interface, before loading org, or you may need to run M-x
> org-reload.

That was it! Thank you.

> I also find it helpful to combine the objective + a note about concrete
> action to take on the objective. The concrete action helps to get
> started on the objective without drowning myself into thinking (but not
> doing) about all the things I need to do on that objective.

Objectives here on my side also have their description which is meant
more as communication, information and instruction to people doing
it. Other notes that are maybe useful for management, thinkering, that
would rather obstruct execution of single step are not written in
those headings meant for execution.

> Would you mind writing a paragraph or two to improve the "5 TODO Items"
> section of the manual? At least, we can inform people that the ability
> to scatter todo items all around the documents does not mean that it has
> to be done.

That would be nice. But me writing it for many would not be. It is
better to define list of various paradigms of planning by group of
people who are here on mailing list. Then such paradigms may be
mentioned or referenced collaboratively.

While this type of planning correlate to me:
https://en.wikipedia.org/wiki/Project_management#Planning

it may not correlate to many other people. So various types of
planning should be presented in the manual.

1. Scattered method, putting notes, tasks in many various places and
   compensating for it with org-agenda

2. Project management as given on Wikipedia could then advise for this
   model: https://en.wikipedia.org/wiki/Waterfall_model#Model and
   describe such in short with reference to WWW hyperlink and advising
   Org users to define the objectives and next steps to be followed
   only if previous steps have been accomplished. It is natural to
   write notes related to action step together. But to avoid placing
   notes or action steps from different scope in one file. When one
   headline TODO have been accomplished then it is followed by next
   TODO headline. This way the steps are chronologically ordered.

   What do you think of that?

3. Project planning template could be included as laid out here:
   https://en.wikipedia.org/wiki/Project_management#Planning
   but in simpler way with the example Org template for some practical
   product such as "bread" in bakery or "software project".

What do you think?

Jean