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

From: Indraneel Majumdar <indraneel@indraneel.info>
To: Bastien <bastien.guerry@wikimedia.fr>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: problem with label in latex export
Date: Wed, 22 Sep 2010 15:05:38 +0530	[thread overview]
Message-ID: <4C99CDEA.9070709@indraneel.info> (raw)
In-Reply-To: <87hbhirvne.fsf@gnu.org>

  Thanks Bastien, this works inline. Please put it in the manual, it's 
just one line. I've spent looking for it every inch of the manual for 
more than a day.

So will you be putting in \phantomsection for inline targets to work? I 
guess if someone is using a <<target>> then it's more likely /not/ to be 
a section heading. Putting it at a section heading doesn't hurt, but not 
having it inline makes for a useless <<target>>. Off course for Latex 
only, so probably should be in the exporter.

Indraneel

On 2010-09-22 14:40, Bastien wrote:
> Hi Indraneel,
>
> Indraneel Majumdar<indraneel@indraneel.info>  writes:
>
>> 11.
>>      #+<<target>>
>>      Some text
>> 12.  More text [[target][go to]]
> You're right that there is a problem.
>
> The usual way of turning radio links invisible is to comment them, but
> Org comments need to be at the beginning of the line, which breaks list
> indentation.  (Btw, no need for the '+' in '#+' -- '#+' is the syntax
> prefix for optional elements like blocks, etc.)
>
> The workaround here is to add (INVISIBLE) after your<<target>>
>
> This works:
>
>> 11.<<target>>(INVISIBLE)
>>      Some text
>> 12. More text [[target][go to]]
> It exports okay in HTML and LaTeX.
>
> I've added a FAQ entry for this -- not sure whether it should go in the
> manual.
>
> Thanks for bringing this up!
>

next prev parent reply	other threads:[~2010-09-22  9:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-10 11:42 problem with label in latex export Indraneel Majumdar
2010-09-21 22:41 ` Bastien
2010-09-22  3:53   ` Indraneel Majumdar
2010-09-22  9:10     ` Bastien
2010-09-22  9:35       ` Indraneel Majumdar [this message]
2010-09-22 10:56       ` Nicolas Goaziou

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=4C99CDEA.9070709@indraneel.info \
    --to=indraneel@indraneel.info \
    --cc=bastien.guerry@wikimedia.fr \
    --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).