From: Markus Grebenstein <post@mgrebenstein.de>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Export <<anchor>> to latex
Date: Fri, 02 Mar 2012 23:09:06 +0100 [thread overview]
Message-ID: <4F514502.1060402@mgrebenstein.de> (raw)
In-Reply-To: <4755.1330719827@alphaville>
Dear Nick,
that is even more than enough ;-)
Thanks a lot! That solves quite a bit of preoblems for me.
I tried to put the anchor in the line of the headline itself and it
worked in orgmode but was not exported as I expected.
Best,
Markus
Am 02.03.2012 21:23, schrieb Nick Dokos:
> 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
>
prev parent reply other threads:[~2012-03-02 22:09 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
2012-03-02 22:09 ` Markus Grebenstein [this message]
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=4F514502.1060402@mgrebenstein.de \
--to=post@mgrebenstein.de \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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).