From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lawrence Bottorff Subject: How to tweak org-log-into-file, how to leverage state history. Date: Sun, 1 Mar 2020 00:57:03 -0600 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000a6b0de059fc59450" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:37665) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1j8IXO-00059A-Te for emacs-orgmode@gnu.org; Sun, 01 Mar 2020 01:57:20 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1j8IXN-0000Lz-JS for emacs-orgmode@gnu.org; Sun, 01 Mar 2020 01:57:18 -0500 Received: from mail-lf1-x12d.google.com ([2a00:1450:4864:20::12d]:35370) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1j8IXN-0000LA-BQ for emacs-orgmode@gnu.org; Sun, 01 Mar 2020 01:57:17 -0500 Received: by mail-lf1-x12d.google.com with SMTP id z9so5390902lfa.2 for ; Sat, 29 Feb 2020 22:57:16 -0800 (PST) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane-mx.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode Mailinglist --000000000000a6b0de059fc59450 Content-Type: text/plain; charset="UTF-8" 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 --000000000000a6b0de059fc59450 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've been trying to understand the whole TODO universe= , now that I've finally tackled it. The ability to create all the vario= us 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 GROKK= ED for issues I'm "thinking hard" about.

M= y frustration is when I create/change a state (all my states have=C2=A0@ fo= r "add log blurb"), the LOGBOOK only allows a single rambling sen= tence, i.e., no paragraphs. For example, I want to start out with my own cu= stom PROPERTIES drawer, then start the text.

To el= aborate, I create a heading and give it the status TOGROK. So I say a lot a= bout this initial=C2=A0state and save it. Then I want to change the state t= o 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 o= f 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 TO= DO state history.

Sure, I could have just done ela= borations as they came to me as text, graphs, pics, whatever under the head= ing, paragraph after paragraph,=C2=A0but then I've lost the whole st= ate change dynamic of attaching new information to a new state, and with it= the tracked history.=C2=A0

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

=
** GROKKING ...My first attempts at tracking issue
:LOGBOOK:
- State "GROKKING" =C2=A0 from "GRO= KKING" =C2=A0 [2020-02-29 Sat 23:50] \\
=C2=A0 Still gro= kking this one.
=C2=A0 But will return to this issue.
- State "G= ROKKING" =C2=A0 from "TOGROK" =C2=A0 =C2=A0 [2020-02-29 Sat = 23:49] \\
=C2=A0 Will "ask around" on this issue.
- State &= quot;TOGROK" =C2=A0 =C2=A0 from =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0[2020-02-29 Sat 23:43] \\
=C2=A0 Aware that I need = to grok this whole thing.

So what can I do with or= g-log-into-drawer's Other option? I tried (org-log-into-drawer=C2=A0 (c= urrent-time)), which is apparently just the same as=C2=A0(org-log-into-draw= er=C2=A0 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
--000000000000a6b0de059fc59450--