From: Adam Porter <adam@alphapapa.net>
To: "Thomas S. Dye" <tsd@tsdye.online>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: How to organize tasks about Worg within Worg documents
Date: Fri, 29 Mar 2024 21:27:55 -0500 [thread overview]
Message-ID: <e737b369-716a-4f46-8817-b680dc1efcfb@alphapapa.net> (raw)
In-Reply-To: <87ttkosj9m.fsf@tsdye.online>
Hi Tom,
On 3/29/24 18:30, Thomas S. Dye wrote:
> Here's another potential solution that I find useful.
>
> d. Keeping tasks under a heading held back from export.
> I have a capture template that saves tasks about the document under a *
> Tasks :no-export: heading. To keep the agenda sane, I don't add the
> file. Instead, I show buffer local tasks with org-sidebar.
Yes, that's a good solution if we want the tasks hidden from the
exported HTML on Worg. I'm not sure if we do want that; that may be
another minor policy decision to be made. (Maybe it's not a big deal,
but a bit of consistency in this regard would make Worg seem more
serious and polished, which might encourage more contribution.)
next prev parent reply other threads:[~2024-03-30 2:28 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 ` 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 ` Adam Porter [this message]
2024-03-30 10:47 ` 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
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=e737b369-716a-4f46-8817-b680dc1efcfb@alphapapa.net \
--to=adam@alphapapa.net \
--cc=emacs-orgmode@gnu.org \
--cc=tsd@tsdye.online \
--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 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).