From: Bernt Hansen <bernt@norang.ca>
To: Sebastian Rose <sebastian_rose@gmx.de>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>,
Ali Tofigh <alix.tofigh@gmail.com>
Subject: Re: Feature suggestion: highlights
Date: Fri, 16 Apr 2010 15:54:51 -0400 [thread overview]
Message-ID: <87vdbrmaus.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: 87r5mfxkl0.fsf@gmx.de
Sebastian Rose <sebastian_rose@gmx.de> writes:
> Ali Tofigh <alix.tofigh@gmail.com> writes:
>> But you still have the problem that once you use a headline, on any
>> level, then you can't continue writing in the same section as before:
>>
>> * headling
>> text text text
>> ********* some todo
>> and now what? Now I have to create a new headline to get out of the
>> deeply nested headline. So I can't continue wrting text after the todo
>> that is directly related to the text above it.
>
>
> Ahhrg - yes. I never use this kind of todo items.
>
> I don't know what the others think of this. But this feels wrong,
> doesn't it? I'd expect an empty line to break out of the todo. Am I
> missing a variable some where?
I believe the 'empty line breaks out' idea is for exporting inline tasks
only - they don't behave that way in regular org files IIRC.
I've tried using inline tasks but they don't work well for my meeting
notes for a few reasons:
- They break the list if I'm making point form notes (which is what I
normally do for meeting notes)
- they look and act like real tasks... so they block marking the
meeting DONE
- they show up in the global task list even if the meeting is DONE and
they were more for information only than real tasks.
Regards,
Bernt
next prev parent reply other threads:[~2010-04-16 20:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-15 20:15 Feature suggestion: highlights Ali Tofigh
2010-04-15 23:21 ` Sebastian Rose
2010-04-16 15:55 ` Ali Tofigh
2010-04-16 19:29 ` Sebastian Rose
2010-04-16 19:54 ` Bernt Hansen [this message]
2010-04-16 21:06 ` Bug in org-inlinetask - was: " Sebastian Rose
2010-04-16 21:32 ` Sebastian Rose
2010-04-16 21:33 ` Bernt Hansen
2010-04-16 21:47 ` Sebastian Rose
2010-04-17 1:17 ` Ali Tofigh
2010-04-17 1:29 ` Bernt Hansen
2010-04-16 0:44 ` Bernt Hansen
2010-04-16 16:00 ` Ali Tofigh
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=87vdbrmaus.fsf@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--cc=alix.tofigh@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=sebastian_rose@gmx.de \
/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).