emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Markus Grebenstein <post@mgrebenstein.de>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: Export <<anchor>> to latex
Date: Fri, 02 Mar 2012 15:23:47 -0500	[thread overview]
Message-ID: <4755.1330719827@alphaville> (raw)
In-Reply-To: Message from Markus Grebenstein <post@mgrebenstein.de> of "Fri, 02 Mar 2012 20:58:53 +0100." <4F51267D.1030903@mgrebenstein.de>

Markus Grebenstein <post@mgrebenstein.de> wrote:

> Dear List,
> 
> I am regularly running into problems with internal links to headings,
> since my document meanwhile is 200pp+ long and I tend to change
> headings.
> 
> Since I loose the ability to jump to the heading, I do not like to use
> the classic latex approach using \label.
> 
> I am wondering why anchors are not exported as a label. Alternatively
> having an "option" for headings would be nice like:
> * Heading [label:anchor]
> 
> Is there a possibility to tweak orgmode to export anchors?
> 
> Thanks in advance,
> 

I may be misunderstanding what you mean, but when I try exporting to latex
the following org file:

--8<---------------cut here---------------start------------->8---

* foo
# <<fooanchor>>

foo text

* bar
# <<baranchor>>

bar text
--8<---------------cut here---------------end--------------->8---

I get the following latex code:

,----
| ...
| \section{foo}
| \label{sec-1}
| \label{fooanchor}
| 
| 
| foo text
| \section{bar}
| \label{sec-2}
| \label{baranchor}
| 
| 
| bar text
| ...
`----

Isn't that enough?

Nick

  reply	other threads:[~2012-03-02 20:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-02 19:58 Export <<anchor>> to latex Markus Grebenstein
2012-03-02 20:23 ` Nick Dokos [this message]
2012-03-02 22:09   ` Markus Grebenstein

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=4755.1330719827@alphaville \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=post@mgrebenstein.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).