Lawrence
On Fri, Feb 28, 2020 at 09:26:06AM -0600, Lawrence Bottorff wrote:
> I can see that an "incident" can be seen as a TODO; indeed, anything event
> can start as a TODO, then move on in status to one of your other
> org-todo-keyword entries. Question: When I start the TODO process, and then
I can see that an "incident" can be seen as a TODO; indeed, anything event
can start as a TODO, then move on in status to one of your other
org-todo-keyword entries. Question: When I start the TODO process, and then
update the status, once or more times, finally, perhaps with DONE, is there
a recor
i have no right to respond as i have 483 scheduleds and 28 deadlines
and i get lost even trying to get one thing done per week, but i just
wanted to add to the advice so far.
there is org-edna for dependencies. org-depend also, but i think it
lacks the feature of scheduling a remote org-id header
back to the list and show the
requirements and your proposed org-mode solution or ask for an org-mode
based solution and you may get some more substantive responses. As it
stands, the possibilities are too broad/open for any real advice.
A lot will depend on what or how you want to use the incident
On Thu, Feb 27, 2020 at 04:55:30PM -0600, Lawrence Bottorff wrote:
> What would be the best way in the Emacs org-mode world to "keep track" of
> "incidents" that might happen in, e.g., a factory setting? Let's say a
> piece of equipment has various things in its life that happen to it:
> breakdown,
What would be the best way in the Emacs org-mode world to "keep track" of
"incidents" that might happen in, e.g., a factory setting? Let's say a
piece of equipment has various things in its life that happen to it:
breakdown, warning, maintenance, etc. that you want to keep track of in an
org-mode w
