From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Sergio Bacelar <sergio.bacelar@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Export org file to pdf: unable to resolve link
Date: Thu, 11 Feb 2016 01:03:43 +0100 [thread overview]
Message-ID: <87fux05d0g.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <30701A91-FEFF-4BAD-B35F-2E155717F91D@gmail.com> (Sergio Bacelar's message of "Wed, 10 Feb 2016 19:10:05 +0000")
Hello,
Sergio Bacelar <sergio.bacelar@gmail.com> writes:
> I am trying with no success to export the most important text from
> Vikas Rawal
> https://github.com/vikasrawal/orgpaper/blob/master/orgpapers.org
> <https://github.com/vikasrawal/orgpaper/blob/master/orgpapers.org> to
> pdf via LaTeX. I tried C-c C-e l o but I obtain always the error
> message “Unable to resolve link readata-code”.
> This happens because the link readapt-code is not working:
>
>
> Code block [[readdata-code]] is an example of such a code block. Note
> ~:results value silent~ switch used in the ~#+begin_src~ line.
>
> #+BEGIN_SRC org
> ,#+NAME: readdata-code
> ,#+BEGIN_SRC R :results value silent
>
> read.data("datafile1.csv",sep=",",header=T)->mydata1
>
>
> ,#+END_SRC
> #+END_SRC
>
> If #+NAME was not inside the SRC block and there was no comma before #+NAME the link should work.
> Does anyone can help me to export this file to pdf?
Couldn't you also copy #+NAME: readdata-code outside of the block?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2016-02-11 0:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 19:10 Export org file to pdf: unable to resolve link Sergio Bacelar
2016-02-11 0:03 ` Nicolas Goaziou [this message]
2016-02-11 10:17 ` Sergio Bacelar
2016-02-11 10:36 ` Nicolas Goaziou
2016-02-11 13:06 ` John Hendy
2016-02-13 2:04 ` Vikas Rawal
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=87fux05d0g.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=sergio.bacelar@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).