emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: "François Pinard" <pinard@iro.umontreal.ca>
To: emacs-orgmode@gnu.org
Subject: "# <<tag>>" should stick to the following text
Date: Sun, 06 May 2012 16:35:08 -0400	[thread overview]
Message-ID: <8662c9rqtq.fsf@mercure.progiciels-bpi.ca> (raw)

Hi, Org people.

I'm not sure I'm using "# <<tag>>" correctly, but my feeling is that it
should stick to the following text in various Org operations.  Let's say
I have something like (as I think it):

--8<---------------cut here---------------start------------->8---
* Some container

  # <<tag1>>
  * Title 1

  # <<tag2>>
  * Title 2
--8<---------------cut here---------------end--------------->8---

If I put # <<tag1>> after "Title 1", say, the generated HTML is such
that using URL#tag1 will position the browser window to the first line
after "Title 1".  Putting it before yields what I expect, that is, the
browser jumps to "Title 1".

However, Org interpret the above as:

--8<---------------cut here---------------start------------->8---
* Some container

  # <<tag1>>
  * Title 1

    # <<tag2>>
  * Title 2
--8<---------------cut here---------------end--------------->8---

putting the # <<tag2>> as a line within the "Title 1" header.  If I
later use 

next             reply	other threads:[~2012-05-06 20:35 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-06 20:35 François Pinard [this message]
2012-05-06 21:18 ` "# <<tag>>" should stick to the following text Nicolas Goaziou
2012-05-07  0:41   ` François Pinard
2012-05-07  1:44     ` François Pinard
2012-05-07  7:10     ` Nicolas Goaziou
2012-05-07  8:24       ` Eric S Fraga
2012-05-07 16:52       ` François Pinard
2012-05-08 14:14       ` Nick Dokos
2012-05-07  1:08   ` Nick Dokos
2012-05-07  5:14     ` Eric S Fraga
2012-05-08  8:33       ` Bastien
2012-05-07  5:34     ` Christian Moe

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=8662c9rqtq.fsf@mercure.progiciels-bpi.ca \
    --to=pinard@iro.umontreal.ca \
    --cc=emacs-orgmode@gnu.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

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