emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Vikas Rawal <vikaslists@agrarianresearch.org>
To: John Hendy <jw.hendy@gmail.com>
Cc: Sergio Bacelar <sergio.bacelar@gmail.com>,
	org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Export org file to pdf: unable to resolve link
Date: Sat, 13 Feb 2016 07:34:31 +0530	[thread overview]
Message-ID: <F56DD8DF-851E-4C0E-BD47-2181A25B83C3@agrarianresearch.org> (raw)
In-Reply-To: <CA+M2ft-LDrvYo03EB7Rs2j1W8cZ68nAZkGoP7Mow_BNpmMm9sA@mail.gmail.com>



> On 11-Feb-2016, at 6:36 pm, John Hendy <jw.hendy@gmail.com> wrote:
> 
> On Thu, Feb 11, 2016 at 4:36 AM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> Hello,
>> 
>> Sergio Bacelar <sergio.bacelar@gmail.com> writes:
>> 
>>> Yes, that will work but I hoped that the file
>>> won't need to be changed to be exported to
>>> pdf.
>> 
>> You may ask for an upstream update, the syntax used in the document is
>> invalid (i.e., an internal link pointing to no active location).
> 
> Echoing this, and I think Vikas would want to know as well since it
> looks like a [awesome] document designed for reproducibility.
> 

My apologies to all for not being able to attend to the fix promptly. As it turned out, I had sometime noticed the bug, fixed it in my local copy and forgotten to push it to the remote. So my local copy was happily compiling.

I have now pushed my latest version. Please see if it compiles for you now.

Since I wrote this manual, I have learnt a few more things, and would like to update the manual. I hope to be able to do it in a few days.

Thanks everyone,

Vikas

      reply	other threads:[~2016-02-13  2:04 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
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 [this message]

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=F56DD8DF-851E-4C0E-BD47-2181A25B83C3@agrarianresearch.org \
    --to=vikaslists@agrarianresearch.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jw.hendy@gmail.com \
    --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).