all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements)
Date: Fri, 29 Mar 2024 17:38:51 -0500	[thread overview]
Message-ID: <040d14ef-13c2-4955-a059-91f29b29008e@alphapapa.net> (raw)
In-Reply-To: <8734s9fjxg.fsf@localhost>

On 3/29/24 04:48, Ihor Radchenko wrote:

>>> Also, we may consider re-using inlinetask style for TODO: entries.
>>>
>>> Rather than
>>> #+begin_center
>>> TODO: Even better, find a volunteer to maintain this information!
>>> #+end_center
>>>
>>> We can do
>>>
>>> **************************** TODO Even better, ...
>>
>> That is a lot of asterisks, and I can't remember if inline tasks are
>> enabled by default.  :)  But in general, sure, I've no objection.  I
>> think that we should have some standard way to encode tasks within Worg
>> documents, regardless of what it is.
> 
> Yeah. And... we do.
> https://orgmode.org/worg/worg-editing.html#orgce51883
> 
> Just a normal heading with TODO keyword.

I'm not sure that page really covers the question of how to present 
tasks about the document within the same document.

Using a normal heading for a task would "commandeer" the structure of 
the document, which I think is a real problem.

ISTM that there are a few potential solutions:

a. Using inline tasks.  Although not enabled by default, they seem to
    solve the problem pretty well.

b. Using commented lines, i.e.

      # TODO: Improve this information.

    Potentially we could even comment Org syntax within the file, like:

      # * TODO Improve this information  :research_needed:

    Which encodes a normal Org heading but as a commented line, so it 	
    wouldn't affect the structure of the document itself.  Of course,
    that would not appear in the exported content, which is probably not
    what we want; but those headings could still be collected, e.g. by
    something like magit-todos.

c. Keeping tasks in a separate file.  We do already have the /todo.org
    file, so maybe this is what we should standardize on, i.e. never
    putting tasks in the documents themselves but only in this file.

Regardless of the decision, I do think that having this stated as a 
policy somewhere would be helpful.

WDYT?


  reply	other threads:[~2024-03-29 22:39 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-23 14:35 [Worg] CSS improvements Adam Porter
2024-03-23 14:49 ` Ihor Radchenko
2024-03-24  6:14   ` Adam Porter
2024-03-24  8:56     ` Ihor Radchenko
2024-03-24  9:28       ` Dr. Arne Babenhauserheide
2024-03-25 14:09       ` Adam Porter
2024-03-26 14:48         ` Ihor Radchenko
2024-03-27  3:20           ` Adam Porter
2024-03-28 11:44             ` Ihor Radchenko
2024-03-28 12:41               ` Adam Porter
2024-03-28 13:18                 ` Ihor Radchenko
2024-03-28 17:53                   ` Adam Porter
2024-03-29  9:48                     ` Ihor Radchenko
2024-03-29 22:38                       ` Adam Porter [this message]
2024-03-29 23:30                         ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Thomas S. Dye
2024-03-30  2:27                           ` How to organize tasks about Worg within Worg documents Adam Porter
2024-03-30 10:47                         ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Ihor Radchenko
2024-03-31 15:43                           ` How to organize tasks about Worg within Worg documents Adam Porter
2024-04-01 11:34                             ` Ihor Radchenko
2024-04-01 18:02                               ` Adam Porter
2024-03-26 22:12         ` [Worg] CSS improvements David Rogers

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=040d14ef-13c2-4955-a059-91f29b29008e@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@posteo.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.