From: Rasmus <rasmus@gmx.us>
To: kyeongsoo.kim@gmail.com
Cc: emacs-orgmode@gnu.org
Subject: Re: Changed behaviours of LaTeX exporter in version 8.0+
Date: Mon, 29 Sep 2014 16:18:30 +0200 [thread overview]
Message-ID: <87ppeewlvt.fsf@gmx.us> (raw)
In-Reply-To: <CACsgZ=pTjadJQsuahCBo0ewvQDxz=L3EGQ-Uu+dXPuPA5MiuSA@mail.gmail.com> (Kyeong Soo Kim's message of "Mon, 29 Sep 2014 20:18:22 +0800")
Hi,
"Kyeong Soo (Joseph) Kim" <kyeongsoo.kim@gmail.com> writes:
> If possible, please let me know where to find the information you provided
> (i.e., without the description filed in the org-mode internal link, its
> export to LaTeX becomes "\ref{...}" instead of "\hyperref{...}").
You can open the info version of the manual with
(info "org")
> I'm currently using Org Manual version 8.2.7c (PDF version), but cannot
> find any relevant information. It's not the matter of whether it's clear or
> not, but there is no such information in the current manual.
>
> I do wonder where you got that information (directly from the source code?).
It may be documented in chapter 4, entitled Hyperlinks.
http://orgmode.org/org.html#Hyperlinks
I don't know if this chapter describes export behavior.
You can skim through org-latex-link if you care. For headlines this
is the relevant part
;; LINK points to a headline. If headlines are numbered
;; and the link has no description, display headline's
;; number. Otherwise, display description or headline's
;; title.
(headline
(let* ((custom-label
(and (plist-get info :latex-custom-id-labels)
(org-element-property :CUSTOM_ID destination)))
(label
(or
custom-label
(format "sec-%s"
(mapconcat
#'number-to-string
(org-export-get-headline-number destination info)
"-")))))
(if (and (not desc)
(org-export-numbered-headline-p destination info))
(format "\\ref{%s}" label)
(format "\\hyperref[%s]{%s}" label
(or desc
(org-export-data
(org-element-property :title destination) info))))))
> Writing a documentation patch could be an option, but first of all, I need
> detailed information on this but currently have not.
Please see
http://orgmode.org/worg/org-contribute.html
for practical details.
—Rasmus
--
To err is human. To screw up 10⁶ times per second, you need a computer
next prev parent reply other threads:[~2014-09-29 14:18 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
2014-09-29 12:18 ` Kyeong Soo (Joseph) Kim
2014-09-29 14:18 ` Rasmus
2014-09-29 14:18 ` Rasmus [this message]
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=87ppeewlvt.fsf@gmx.us \
--to=rasmus@gmx.us \
--cc=emacs-orgmode@gnu.org \
--cc=kyeongsoo.kim@gmail.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).