From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: Using org-mode for Research and Notetaking
Date: Mon, 18 Jul 2011 15:21:46 +0200 [thread overview]
Message-ID: <80pql73es5.fsf@somewhere.org> (raw)
In-Reply-To: 874o2jbw0b.fsf@fastmail.fm
Hi Matt,
Matt Lundin wrote:
> Bastien <bzg-whniv8GeeGkdnm+yROfE0A@public.gmane.org> writes:
>> "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org> writes:
>>
>>>> * !TODO This would be an inline task, not a headline
>>>
>>> I've no clear cut opinion on this right now. Maybe yes, maybe not.
>>> Though, there are differences between inline tasks and headlines:
>>
>> I'm talking about the way they _look_. So many asterisks looks cumbersome
>> to mee, and I'd favor a non-intrusive syntax like the one proposed above.
>
> In my experience, most of the asterisks are made invisible by
> org-hide-face. E.g.,
>
> * ** TODO A task
> Some notes about the task that are not part of the text.
> * ** END
>
>> My question was: what is the rationale behind using so many asterisks?
>>
>> I can think of three things:
>>
>> 1. people want inline tasks with possibly no TODO keyword
>
> This is often how I use them --- to insert a "drawer" of notes that is
> visible but will not be exported.
Why do you say it wouldn't be exported just because it has no TODO keyword?
At least, not in the default settings of the export, right?
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2011-07-18 13:21 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-10 11:09 RFC: Revisit org-export-content-div (in the context of org-s5) Jambunathan K
2011-07-10 11:28 ` Jambunathan K
2011-07-11 11:44 ` Bastien
2011-07-11 19:55 ` Using org-mode for Research and Notetaking Florian Beck
2011-07-12 14:23 ` John Hendy
2011-07-14 18:09 ` Florian Beck
2011-07-12 14:28 ` Giovanni Ridolfi
2011-07-13 8:55 ` Bastien
2011-07-13 9:59 ` Sebastien Vauban
2011-07-13 11:20 ` Bastien
2011-07-13 12:20 ` Sebastien Vauban
2011-07-13 13:43 ` Nicolas Goaziou
2011-07-16 11:40 ` Bastien
2011-07-18 12:42 ` Matt Lundin
2011-07-18 13:21 ` Sebastien Vauban [this message]
2011-07-18 14:53 ` Matt Lundin
2011-07-18 14:03 ` Sebastien Vauban
2011-07-18 14:58 ` Bastien
2011-07-14 18:40 ` Florian Beck
2011-07-14 18:59 ` Thomas S. Dye
2011-07-18 22:54 ` Bastien
2011-07-18 23:59 ` Thomas S. Dye
2011-07-19 1:34 ` Florian Beck
2011-07-26 11:27 ` Bastien
2011-07-26 14:17 ` Florian Beck
2011-07-26 15:15 ` Thomas S. Dye
2011-07-26 17:41 ` Christian Moe
2011-07-11 11:44 ` RFC: Revisit org-export-content-div (in the context of org-s5) Bastien
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=80pql73es5.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.org \
/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).