emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: bar tomas <bartomas@gmail.com>
To: Matt Lundin <mdl@imapmail.org>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Tagging a region of text without creating a branch
Date: Fri, 9 Oct 2009 15:05:59 +0100	[thread overview]
Message-ID: <fdcd75820910090705n1f3651e6ka5ae53fd21956a4a@mail.gmail.com> (raw)
In-Reply-To: <87r5tc919n.wl@imapmail.org>

Thanks very much for your reply and your help.
I also think in terms of containers, but I was trying to figure out if
it is possible to have a container that has both subcontainers and
content that is not contained in a subcontainer.
For instance, in XML, this is the notion of an element with 'mixed
content'(subelements+character content). For example:

<item1 priority='A' >
general stuff  about item1
<subItem1> about subItem1 </subItem1>
more general stuff about item1

I suppose, this kind of structure is not possible in orgmode?
you'd have to create 'artificial' subheadings:

* item1 [#A]
** general stuff item1
general stuff  about item1
about subItem1
** general stuff item1
more general stuff about item1

So, a container in orgmode can have either subcontainers or text but
not a mixture of both? Is this right?

Thanks also for the tip about freex. it looks interesting, pity its
not compatible with orgmode.
I'll have a look at inline tasks as you suggest.
Thanks again

On Fri, Oct 9, 2009 at 1:53 PM, Matt Lundin <mdl@imapmail.org> wrote:
> bar tomas wrote:
>> Hi,
>> Maybe I use orgmode in a quirky way, but I often find the need of
>> tagging internal regions.
>> I don't have a problem with a creating a heading but what I find
>> sometimes inconvenient is that implicitely everything that comes after
>> the created headingis in it's scope until the next heading.
>> I mean, don't you ever come across a situation like the following?
>> * idea1
>> Notes about idea1
>> More notes about idea1
>> still more about idea1
> IMO, this is precisely the strength of outlines. You can create
> subheadings to organize/categorize your thoughts. But perhaps I still
> misunderstand what you are trying to do? I like to think of org
> outline headings as data containers or "database records." You attach
> metadata (tags, todos, properties, etc.) to the container.
>> and you'd like to tag the second line (and only second line with
>> :tellSueAboutIt:). If I understand correctly the only way to do this
>> with headings is:
>> * idea1
>> Notes about idea1
>> ** :tellSueAboutIt:
>> More notes about idea1
>> ** :DontTellSueAboutIt:
>> still more about idea1
>> This is very cumbersome and conceptually confusing.z It would be
>> really convenient to sometimes be able to tag an internal region.
>> Someone mentioned inline tasks. Is this possible with inline tasks?
> Yes. As Bernt suggested, I think inline tasks would achieve your ends
> very well here. Inline tasks act like normal headlines for the
> purposes of the agenda --- i.e., they will appear in your searches.
> But they will not be exported. Neither will they open with other
> headlines during cycling.
> You can create inline tasks by creating really deep outline headlings
> (I believe the default is 15).
> Here's an example:
> * idea1
>  Notes about idea1
> *                   *** An inline task :tellSueAboutIt:
>  More notes about idea1
> *                   *** Another inline task :DontTellSueAboutIt:
>  still more about idea1
> See the variables org-inlinetask-export and org-inlinetask-min-level.
> BTW, There is a mode (freex-mode) that uses pymacs and an external
> database to enable tagging of selected "nuggets" of text. But I don't
> believe that it works with org-mode. I you don't mind the external
> dependencies, you might want to check it out.
> http://www.emacswiki.org/cgi-bin/emacs/FreexMode
> Hope this helps!
> Matt

  reply	other threads:[~2009-10-09 14:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-08 16:06 Tagging a region of text without creating a branch bar tomas
2009-10-08 18:10 ` Matt Lundin
2009-10-08 20:18   ` Bernt Hansen
     [not found]     ` <1f38ae890910090023h2b5cb320y1d2d778c1037d752@mail.gmail.com>
2009-10-09  7:26       ` Andrew Stribblehill
2009-10-09 13:19         ` Bernt Hansen
     [not found]   ` <fdcd75820910090229v39ec6e47m1037cb46afde19a5@mail.gmail.com>
2009-10-09 12:53     ` Matt Lundin
2009-10-09 14:05       ` bar tomas [this message]
2009-10-09 14:43         ` Stephan Schmitt
2009-10-09 15:01           ` bar tomas
2009-10-09 17:45         ` Carsten Dominik
2009-10-09 17:58           ` Matthew Lundin
2009-10-10 14:56             ` Carsten Dominik
2009-10-10 15:39               ` Matt Lundin
2009-10-12  7:29                 ` Carsten Dominik
2009-10-12 13:14                   ` Matt Lundin
2009-10-12 13:27                     ` Carsten Dominik
2009-10-12 13:40                       ` Matthew Lundin

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:

  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=fdcd75820910090705n1f3651e6ka5ae53fd21956a4a@mail.gmail.com \
    --to=bartomas@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.org \


* 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


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).