From: Adam Porter <adam@alphapapa.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: How to organize tasks about Worg within Worg documents
Date: Sun, 12 May 2024 08:42:35 -0500 [thread overview]
Message-ID: <5e94364b-69df-47f7-9979-ea891d24dab1@alphapapa.net> (raw)
In-Reply-To: <87le4frzox.fsf@localhost>
On 5/12/24 07:18, Ihor Radchenko wrote:
> I looked into this further, and found
> exporters/taskjuggler/ox-taskjuggler.org
>
> that has whole "TODO" subtrees hidden with :noexport: tag.
>
> Such half-ready subtrees are not really ready for normal viewing and are
> mostly a material for WORG hackers to work on. Not sure how they fit
> into the discussed todo records and notes concept.
Seems like a reasonable solution in that case.
next prev parent reply other threads:[~2024-05-12 13:43 UTC|newest]
Thread overview: 23+ 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 ` How to organize tasks about Worg within Worg documents (was: Re: [Worg] CSS improvements) Adam Porter
2024-03-29 23:30 ` 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-05-12 12:18 ` Ihor Radchenko
2024-05-12 13:42 ` Adam Porter [this message]
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=5e94364b-69df-47f7-9979-ea891d24dab1@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.