From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id tI/CIwoOVF+mPgAA0tVLHw (envelope-from ) for ; Sat, 05 Sep 2020 22:15:38 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id iCs8HwoOVF8+dAAAbx9fmQ (envelope-from ) for ; Sat, 05 Sep 2020 22:15:38 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id BE0469403D2 for ; Sat, 5 Sep 2020 22:15:37 +0000 (UTC) Received: from localhost ([::1]:59202 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kEgTA-0000Wv-5Q for larch@yhetil.org; Sat, 05 Sep 2020 18:15:36 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:40486) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kEgSd-0000Wl-Uj for emacs-orgmode@gnu.org; Sat, 05 Sep 2020 18:15:03 -0400 Received: from mail-ot1-x32f.google.com ([2607:f8b0:4864:20::32f]:45766) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kEgSb-0004jP-A0 for emacs-orgmode@gnu.org; Sat, 05 Sep 2020 18:15:03 -0400 Received: by mail-ot1-x32f.google.com with SMTP id g96so9137418otb.12 for ; Sat, 05 Sep 2020 15:15:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=felesatra-moe.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oyixYKkm6K+ZR7jmU9CTY1RbMxExCAgxBqlsYX0WdYU=; b=NDbF5SmURjd6imNcUvphypJCMNCpt7eQp1Jvi3BswsOq4uQ6AH+30HLupSSPY9/Kga t+D4IxXtM/fl1RwPmGeLttn4WDynMy902vSOAcodvUwn+O50+c5Kj6YNvj4eHb0WN0lk GkAnlru4hXEOkineWhAGLIKMpr+LA8/1K5snp/cWkd8BwmG9XAKpSYPRX0J1HZwdPdqe QoOLKx1kSD0g+r7Oh/BG1oS4sNzyJezRbZDQta+5sA921biG5TjpP3njaoGGWZvklhuh nUsjjiTyMHtT5DXb01dshNBPSeBdMPuKXyqp55yZ+w0ruT2HD7+u3jsSfy7w4nQ8KyC/ fEag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=oyixYKkm6K+ZR7jmU9CTY1RbMxExCAgxBqlsYX0WdYU=; b=WllS3GCpBeX0gRfnm1qTCHTgGp7rVAt9XnqOgZkiHxwCE5BHaW3LBENGzMmbc2qKAb 7d3oQm7HVH1M3XhLo04HTRV2C/Qk2Gj2TFoCxcg484+L+Tfx2/17qC8NwN2atwc76m6y 5ZSHhSvfISYJQXgJbDzFpnk0O/lti8cbzj7lv1bCA75bI3bdqMlRnqUL7Jhe2WUvKQAF 9fBpiQzNDhVnlKwu+lK7pgg7p1PIpnXTjmSHrTZOulmPNUpp1HOji0yHYz85UfQI6u34 F7W0QGcfF6pXpJFg5YmAJVE7GHkeuQQwflGw60UsnDqYiaQApSiVyA86ywbQD2y8Ct5o pUzA== X-Gm-Message-State: AOAM532jQ1qTNxLi+dg1l2d39hrD44JXw0+6xj2XWjeBmZ3u8i/B+HSs plNKgECtVhSDV8dQ/7ljZmqbH3/uN+Y6Na4hL4X1eA== X-Google-Smtp-Source: ABdhPJz+wOCXQYkC0xr7U7446W9VL299gN2wMugjgCWlTntKrfNMe6wIxV0GpS3Ro51s+McsXI1s6XGHTKxiIlvjd94= X-Received: by 2002:a9d:73d4:: with SMTP id m20mr9489851otk.227.1599344099614; Sat, 05 Sep 2020 15:14:59 -0700 (PDT) MIME-Version: 1.0 References: <87zh6eymxs.fsf@localhost> In-Reply-To: <87zh6eymxs.fsf@localhost> From: Allen Li Date: Sat, 5 Sep 2020 22:14:48 +0000 Message-ID: Subject: Re: [feature request] A new cookie type [!] showing the last note taken To: Ihor Radchenko Content-Type: multipart/alternative; boundary="000000000000ee797c05ae985053" Received-SPF: pass client-ip=2607:f8b0:4864:20::32f; envelope-from=darkfeline@felesatra.moe; helo=mail-ot1-x32f.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Org Mode List Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=felesatra-moe.20150623.gappssmtp.com header.s=20150623 header.b=NDbF5SmU; dmarc=none; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-Spam-Score: -1.21 X-TUID: zrddnBtzgG26 --000000000000ee797c05ae985053 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sat, Aug 29, 2020 at 6:42 AM Ihor Radchenko wrote: > > Over the years of using Org I often have a need to add a short note > about how to proceed with some task: > > ***** REVIEW check again, subscribe | sindresorhus/awesome: =F0=9F=98=8E = Awesome > lists about all kinds of interesting topics :BOOKMARK: > :PROPERTIES: > :CREATED: [2020-03-15 Sun 18:59] > :Source: https://github.com/sindresorhus/awesome > :END: > :LOGBOOK: > CLOCK: [2020-03-17 Tue 16:18]--[2020-03-17 Tue 17:46] =3D> 1:28 > CLOCK: [2020-03-17 Tue 16:03]--[2020-03-17 Tue 16:18] =3D> 0:15 > - Refiled on [2020-03-16 Mon 23:59] > :END: > > In the above example, the short note is "check again, subscribe". > The note is not fixed, but changes as I progress with completing the > task. > Everyone has their own workflows, but I think the way you are approaching this problem is "wrong". Under the GTD methodology, there is the concept of a project (some higher goal to be achieved) and next actions (the concrete tasks to do next to achieve the project). You would only track the next action in your regular toto list. In Org mode, this would look like: * PROJECT make babel support org file links in header args (:file or :dir) ** TODO Finish the text prop org-mode My anecdotal impression is that many people using Org do this (see https://orgmode.org/worg/org-gtd-etc.html), so they have no need for a "last note taken embedded in headline" feature. As a practical matter, I would find it inconvenient to have both the "last note take"/"next action" and the overall project headline appear in the agenta view because it makes the text too wide. If I need to associate the next action with the overall project, I take advantage of the CATEGORY property: * PROJECT make babel support org file links in header args (:file or :dir) :PROPERTIES: :CATEGORY: BabelLinks :END: ** TODO Finish the text prop org-mode Which would show in the agenda as: BabelLinks: TODO Finish the text prop org-mode I have only been partially paying attention to this discussion thread, but this sounds like both a feature with limited appeal and significant complexity to implement, so I would suggest implementing it yourself for your own use case, and then bringing it to the mailing list to share. Once you have a dozen people using it, it will likely have developed into a mature enough form to include in Org mode. Just my 2 cents. > This is even more useful for delegated or HOLD tasks where I often need > to add a short note why the task is delegated or put on hold: > > ** HOLD Finish the text prop org-mode | make babel support org file links > in header args (:file or :dir) > [[id:468e0645-68aa-4e14-86de-e5ce153538e3][[2017-09-22 Fri] > CuNbARBshearstrength]] :HOLD: > :PROPERTIES: > :CREATED: [2020-07-20 Mon 16:53] > :SHOWFROMDATE: 2020-08-15 > :END: > :LOGBOOK: > - State "HOLD" from "NEXT" [2020-08-10 Mon 15:16] \\ > Finish the text prop org-mode > - Refiled on [2020-07-20 Mon 17:15] > CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D> 0:01 > :END: > > Seeing this note directly in the headline without a need to dig into the > task body / LOGBOOK drawer is really handy. > > In this last example, I had to duplicate the note taken using built-in > note mechanism into headline, which was inconvenient. It would be handy > if I could simply add a [!] cookie (similar to [/] or [%] cookies) to > the headline to show the last note taken for this task. Then, I could > easily see the reason why the task is blocked or what I am supposed to > do with the task right in agenda view or in the folded headline. > Something like the following > > ** HOLD [!] make babel support org... :HOLD: > :LOGBOOK: > - State "HOLD" from "NEXT" [2020-08-10 Mon 15:16] \\ > Finish the text prop org-mode > - Refiled on [2020-07-20 Mon 17:15] > CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D> 0:01 > :END: > > The cookie would be replaced by the last note text, according to > user-defined format (say, "[%s] |"): > > ** HOLD [Finish the text prop org-mode] | make babel support org... :HOLD= : > :LOGBOOK: > - State "HOLD" from "NEXT" [2020-08-10 Mon 15:16] \\ > Finish the text prop org-mode > - Refiled on [2020-07-20 Mon 17:15] > CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D> 0:01 > :END: > > What do you think? > > Best, > Ihor > > --000000000000ee797c05ae985053 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sat, Aug 29, 2020 at 6:42 AM Ihor Radc= henko <yantar92@gmail.com> = wrote:

Over the years of using Org I often have a need to add a short note
about how to proceed with some task:

***** REVIEW check again, subscribe | sindresorhus/awesome: =F0=9F=98=8E Aw= esome lists about all kinds of interesting topics :BOOKMARK:
:PROPERTIES:
:CREATED: [2020-03-15 Sun 18:59]
:Source: https://github.com/sindresorhus/awesome
:END:
:LOGBOOK:
CLOCK: [2020-03-17 Tue 16:18]--[2020-03-17 Tue 17:46] =3D>=C2=A0 1:28 CLOCK: [2020-03-17 Tue 16:03]--[2020-03-17 Tue 16:18] =3D>=C2=A0 0:15 - Refiled on [2020-03-16 Mon 23:59]
:END:

In the above example, the short note is "check again, subscribe".=
The note is not fixed, but changes as I progress with completing the
task.

Everyone has their own workflows,= but I think the way you are approaching this problem is "wrong".= =C2=A0 Under the GTD methodology, there is the concept of a project (some h= igher goal to be achieved) and next actions (the concrete tasks to do next = to achieve the project).=C2=A0 You would only track the next action in your= regular toto list. In Org mode, this would look like:

=
* PROJECT=C2=A0make babel support org file links in header args (:file= or :dir)
** TODO=C2=A0Finish the text prop org-mode
My anecdotal impression is that many people using Org do this = (see=C2=A0https://org= mode.org/worg/org-gtd-etc.html), so they have no need for a "last = note taken embedded in headline" feature.=C2=A0 As a practical matter,= I would find it inconvenient to have both the "last note take"/&= quot;next action" and the overall project headline appear in the agent= a view because it makes the text too wide.=C2=A0 If I need to associate the= next action with the overall project, I take advantage of the CATEGORY pro= perty:

* PROJECT=C2=A0make babel support org file = links in header args (:file or :dir)
:PROPERTIES:
:CATE= GORY: BabelLinks
:END:
** TODO=C2=A0Finish the text pro= p org-mode

Which would show in the agenda as:

BabelLinks: TODO=C2=A0Finish the text prop org-mode

I have only been partially paying attention to this = discussion thread, but this sounds like both a feature with limited appeal = and significant complexity to implement, so I would suggest implementing it= yourself for your own use case, and then bringing it to the mailing list t= o share.=C2=A0 Once you have a dozen people using it, it will likely have d= eveloped into a mature enough form to include in Org mode.

Just my 2 cents.


This is even more useful for delegated or HOLD tasks where I often need
to add a short note why the task is delegated or put on hold:

** HOLD Finish the text prop org-mode | make babel support org file links i= n header args (:file or :dir) [[id:468e0645-68aa-4e14-86de-e5ce153538e3][[2= 017-09-22 Fri] CuNbARBshearstrength]] :HOLD:
:PROPERTIES:
:CREATED: [2020-07-20 Mon 16:53]
:SHOWFROMDATE: 2020-08-15
:END:
:LOGBOOK:
- State "HOLD"=C2=A0 =C2=A0 =C2=A0 =C2=A0from "NEXT"=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [2020-08-10 Mon 15:16] \\
=C2=A0 Finish the text prop org-mode
- Refiled on [2020-07-20 Mon 17:15]
CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D>=C2=A0 0:01 :END:

Seeing this note directly in the headline without a need to dig into the task body / LOGBOOK drawer is really handy.

In this last example, I had to duplicate the note taken using built-in
note mechanism into headline, which was inconvenient. It would be handy
if I could simply add a [!] cookie (similar to [/] or [%] cookies) to
the headline to show the last note taken for this task. Then, I could
easily see the reason why the task is blocked or what I am supposed to
do with the task right in agenda view or in the folded headline.
Something like the following

** HOLD [!] make babel support org... :HOLD:
:LOGBOOK:
- State "HOLD"=C2=A0 =C2=A0 =C2=A0 =C2=A0from "NEXT"=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [2020-08-10 Mon 15:16] \\
=C2=A0 Finish the text prop org-mode
- Refiled on [2020-07-20 Mon 17:15]
CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D>=C2=A0 0:01 :END:

The cookie would be replaced by the last note text, according to
user-defined format (say, "[%s] |"):

** HOLD [Finish the text prop org-mode] | make babel support org... :HOLD:<= br> :LOGBOOK:
- State "HOLD"=C2=A0 =C2=A0 =C2=A0 =C2=A0from "NEXT"=C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 [2020-08-10 Mon 15:16] \\
=C2=A0 Finish the text prop org-mode
- Refiled on [2020-07-20 Mon 17:15]
CLOCK: [2020-07-20 Mon 16:53]--[2020-07-20 Mon 16:54] =3D>=C2=A0 0:01 :END:

What do you think?

Best,
Ihor

--000000000000ee797c05ae985053--