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

From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Yasushi SHOJI <yasushi.shoji@gmail.com>,
	emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: exporting a big project in multiple files to both pdf and html
Date: Thu, 01 Feb 2018 13:56:32 +0100	[thread overview]
Message-ID: <874ln0yikf.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2inbgao6a.fsf@charm-ecran.irisa.fr> (Alan Schmitt's message of "Thu, 01 Feb 2018 13:29:17 +0100")

Hello,

Alan Schmitt <alan.schmitt@polytechnique.org> writes:

> On 2018-02-01 20:09, Yasushi SHOJI <yasushi.shoji@gmail.com> writes:
>
>>> How do I change the link in the second headline so that I can split the
>>> second headline into its own file and export it by itself?
>>
>> Using [[*A headline]] ?
>>
>> I might be still missing something but I got following:
>>
>> $ cat a.org
>> * A headline
>>
>> This is the first file.
>>
>> #+INCLUDE: b.org :minlevel 1
>>
>> $ cat b.org
>> * Second headline
>>
>> The first headline is number [[*A headline]]
>
> …
>
>> hmm... latex export will generate \ref{sec:\#head}
>> if you have CUSTOM_ID set.  html exporter works, though.
>
> Not here. If I try to export the second file (the one with the link to
> the first file), I get an error:
>
> user-error: Unable to resolve link: "*A headline"
>
> This is why I think I need to have the target file name in the link when
> exporting it as a standalone file.

If you don't mind broken links, there's also
`org-export-with-broken-links'.

Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2018-02-01 12:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-25 17:37 exporting a big project in multiple files to both pdf and html Alan Schmitt
2018-02-01  2:17 ` Yasushi SHOJI
2018-02-01  8:45   ` Alan Schmitt
2018-02-01 11:09     ` Yasushi SHOJI
2018-02-01 12:29       ` Alan Schmitt
2018-02-01 12:56         ` Nicolas Goaziou [this message]
2018-02-01 13:47           ` Alan Schmitt
2018-02-02  0:38         ` Yasushi SHOJI
2018-02-02  7:41           ` Alan Schmitt
2018-02-02  9:41             ` Yasushi SHOJI
2018-02-02 13:13               ` Alan Schmitt

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=874ln0yikf.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=alan.schmitt@polytechnique.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=yasushi.shoji@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

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).