emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode Mailinglist <emacs-orgmode@gnu.org>
Subject: How to tweak org-log-into-file, how to leverage state history.
Date: Sun, 1 Mar 2020 00:57:03 -0600	[thread overview]
Message-ID: <CAFAhFSXKR3DNuFadGx3C8BrsqdTWeuyRu_BKy1xnv-uAEZDwEA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2308 bytes --]

I've been trying to understand the whole TODO universe, now that I've
finally tackled it. The ability to create all the various states (I haven't
tried SEQ of state groups yet) on an issue entered as a heading in an org
file and then change the status of that heading is marvelous. For example,
I've created states TOGROK, GROKKING, and GROKKED for issues I'm "thinking
hard" about.

My frustration is when I create/change a state (all my states have @ for
"add log blurb"), the LOGBOOK only allows a single rambling sentence, i.e.,
no paragraphs. For example, I want to start out with my own custom
PROPERTIES drawer, then start the text.

To elaborate, I create a heading and give it the status TOGROK. So I say a
lot about this initial state and save it. Then I want to change the state
to GROKKING when I've something new to say. Then I "change" to GROKKING
again -- because some new thing occurs to me. After maybe a few of those, I
change to GROKKED and finalize this whole heading-as-issue. This is exactly
what I want, because this heading-as-issue is leveraging the TODO state
history.

Sure, I could have just done elaborations as they came to me as text,
graphs, pics, whatever under the heading, paragraph after paragraph, *but
then I've lost the whole state change dynamic of attaching new information
to a new state, and with it the tracked history. *

So I see org-log-into-drawer has three possible values in its customize
buffer: nil, LOGBOOK, and Other. The LOGBOOK option allows the nice (but
limited to one sentence) logging of each change of state, creating a history

** GROKKING ...My first attempts at tracking issue
:LOGBOOK:
- State "GROKKING"   from "GROKKING"   [2020-02-29 Sat 23:50] \\
  Still grokking this one.
  But will return to this issue.
- State "GROKKING"   from "TOGROK"     [2020-02-29 Sat 23:49] \\
  Will "ask around" on this issue.
- State "TOGROK"     from              [2020-02-29 Sat 23:43] \\
  Aware that I need to grok this whole thing.

So what can I do with org-log-into-drawer's Other option? I tried
(org-log-into-drawer  (current-time)), which is apparently just the same
as (org-log-into-drawer  t), i.e., just a LOGBOOK entry happened.

Is there something that can happen in sub-headings that keeps track of the
state history of the main heading?

LB

[-- Attachment #2: Type: text/html, Size: 2760 bytes --]

                 reply	other threads:[~2020-03-01  6:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=CAFAhFSXKR3DNuFadGx3C8BrsqdTWeuyRu_BKy1xnv-uAEZDwEA@mail.gmail.com \
    --to=borgauf@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).