emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Mon, 29 Sep 2014 12:09:26 +0200	[thread overview]
Message-ID: <877g0mybzd.fsf@gmx.us> (raw)
In-Reply-To: CACsgZ=omEgp_-FOrt-6bao5QL4c1yadg+nFnmZ=srW1hEvgQqA@mail.gmail.com

Hi Kyeong,

"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:

> Hello,
> On Mon, Sep 29, 2014 at 4:53 PM, Rasmus <rasmus@gmx.us> wrote:
>>
>>
>
>> If you don't want to use hyperref (i) make sure your sections are
>> numbered (e.g. #+OPTIONS: num:5) and (ii) make sure that you are not
>> giving links a description.  Here's an example:
>>
>> * test my heading
>> :PROPERTIES:
>> :CUSTOM_ID: t
>> :END:
>> [[*test my heading][my funky label]]
>> [[*test my heading]]
>> [[#t]]
>>
>> →
>>
>> \section{test my heading}
>> \label{sec-1}
>> \hyperref[sec-1]{my funky label}
>> \ref{sec-1}
>> \ref{sec-1}
>>
>> —Rasmus
>>
>> --
>> May the Force be with you
>>
>>
>>
> This is exactly what I wanted to do for cross-referencing in LaTeX export.
> With this, now I can use my org files as I did with version 7.x (except for
> the description in the link).
>
> It would have been much better to have this information in the manual (like
> those for cross-referencing in LaTeX in the older version of manual).
> Or, is this already described there?

If it's unclear, please consider one of the following:

   1. Writing a documentation patch — especially if you have assigned
      copyright to FSF For Emacs changes.
   2. Explain exactly where you would have expected to find this
      information and/or where the manual is unclear.

Thanks,
Rasmus

-- 
However beautiful the theory, you should occasionally look at the evidence

  reply	other threads:[~2014-09-29 11:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-18  4:50 Changed behaviours of LaTeX exporter in version 8.0+ Kyeong Soo (Joseph) Kim
2014-09-18  7:07 ` Kyeong Soo (Joseph) Kim
2014-09-18  7:32   ` Kyeong Soo (Joseph) Kim
2014-09-18 16:10     ` Richard Lawrence
     [not found]       ` <CACsgZ=r1vzPQg1KB3N7j6Mn+nyu=PUrxJCeRr5ebqmpywsQ0bg@mail.gmail.com>
2014-09-19 15:49         ` Richard Lawrence
2014-09-20 15:32           ` Kyeong Soo (Joseph) Kim
2014-09-22 16:00             ` Nicolas Goaziou
2014-09-23  3:03               ` Kyeong Soo (Joseph) Kim
2014-09-27 22:01                 ` Nicolas Goaziou
2014-09-29  4:51                   ` Kyeong Soo (Joseph) Kim
2014-09-29  7:07                     ` Nicolas Goaziou
2014-09-29  7:57                       ` Kyeong Soo (Joseph) Kim
2014-09-29  8:53                         ` Rasmus
2014-09-29  9:59                           ` Kyeong Soo (Joseph) Kim
2014-09-29 10:09                             ` Rasmus [this message]
2014-09-29 12:18                               ` Kyeong Soo (Joseph) Kim
2014-09-29 14:18                                 ` Rasmus
2014-09-29 14:18                                 ` Rasmus
2014-10-01  9:39                                   ` Kyeong Soo (Joseph) Kim
2014-09-18 15:47   ` Richard Lawrence
  -- strict thread matches above, loose matches on Subject: below --
2014-09-17 14:54 Kyeong Soo (Joseph) Kim
2014-09-17 19:01 ` 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=877g0mybzd.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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
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).