emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: Matt Lundin <mdl@imapmail.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Tagging a region of text without creating a branch
Date: Thu, 08 Oct 2009 16:18:16 -0400	[thread overview]
Message-ID: <87tyy9r65z.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <m263apah9v.fsf@fastmail.fm> (Matt Lundin's message of "Thu\, 08 Oct 2009 14\:10\:20 -0400")

Matt Lundin <mdl@imapmail.org> writes:

> bar tomas <bartomas@gmail.com> writes:
>
>> Is it possible to tag a region of text without creating a new branch?
>> I mean, for instance, if I have the following orgmode document structure:
>>
>> * item1
>> this is about item 1
>> bla bla
>> more about item1
>>
>> I'd like to give a tag to the bit 'bla bla', but the scope of the tag
>> should not include 'more about item 1'; 
>
> Just curious: what would be the advantage of tagging a region of text
> rather than creating subheadings?
>
> E.g.,
>
> --8<---------------cut here---------------start------------->8---
> * item1
> ** this is about item 1 
> about item one
> ** bla bla                      :urgent:
> More bla bla
> ** More about item1
> more about item1
> --8<---------------cut here---------------end--------------->8---
>
> Since org mode relies on the hierarchical structure of outlines, all of
> the subheadings are part of the tree beginning with item1.
>
> Also, how would a region of tagged text appear in the agenda? The agenda
> depends on the association of metadata with headlines.

Tags go with headlines.  The only way to do what you want is with inline
tasks like this:

,----[ .emacs ]
| (require 'org-inlinetask)
`----

,----[ test.org ]
| 
| * item1
| this is about item 1
| *************** subitem1					     :urgent:
| bla bla
| *************** not urgent
| more about item1
`----

HTH

-Bernt

  reply	other threads:[~2009-10-08 20:18 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 [this message]
     [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
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:
  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=87tyy9r65z.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=mdl@imapmail.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).