From: Scott Otterson <scotto@sharpleaf.org>
To: Scott Otterson <scotto@sharpleaf.org>,
"Emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Bug: Latex export fails with link in headline
Date: Sat, 3 Dec 2016 16:04:54 +0100 [thread overview]
Message-ID: <CAPY3P0TJRgL3Wn77aFN9QU6Q1+138FHxVcjiTQJRFFA0OkjoEA@mail.gmail.com> (raw)
In-Reply-To: <CAPY3P0S93+nO2H3OS86R6N592M6Mop9GvgTPJJp896BvwwvJjg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1761 bytes --]
Hi Nicolas,
Could you please check the .tex output you got when exported my .org file
example (attached again)? In the .tex I get (also attached), it's clear
that org-mode has forgotten to escape the '#' in the URL. In headlink.tex,
if I replace '#' with ''\#', then latexmk can successfully make a pdf.
Do you see something different?
Thanks,
Scott
On Tue, Nov 29, 2016 at 1:57 PM, Scott Otterson <scotto@sharpleaf.org>
wrote:
> Very strange. I moved to a different Windows machine, totally reinstalled
> elpa/melpa, and the tmp.org file that emailed the list still failed. I
> even copied tmp.org out of my email to be sure we're looking at the same
> thing.
>
> Could it be something like you're running Linux and I'm running Windows,
> or like I'm running TexLive and you're running MikTex? I've attached the
> output of M-x report-emacs-bug so you can see my whole setup.
>
> I've also attached a different oddly crashing org file, and the latex
> error buffer I get after typing C-c C-e l o
>
> Scott
>
> On Mon, Nov 28, 2016 at 12:26 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr>
> wrote:
>
>> Hello,
>>
>> Scott Otterson <scotto@sharpleaf.org> writes:
>>
>> > Latex export sometimes fails when I put a link in a headline Usually,
>> > links in headlines work fine but below is an example that doesn't (error
>> > message in emacs buffer attached); If I remove the link, the export is
>> > successful.
>> >
>> > -- tmp.org ------------------------------------------------------------
>> -----
>> >
>> > * Some section [[
>> > http://orgmode.org/manual/Column-groups.html#Column-groups][A random
>> link]]
>> >
>> > - Item A
>> > - Item B
>> > - Item C
>>
>> FWIW I cannot reproduce it.
>>
>> Regards,
>>
>> --
>> Nicolas Goaziou
>>
>
>
[-- Attachment #1.2: Type: text/html, Size: 3276 bytes --]
[-- Attachment #2: headlink.org --]
[-- Type: application/octet-stream, Size: 133 bytes --]
* Some section [[http://orgmode.org/manual/Column-groups.html#Column-groups][A random link]]
- Item A
- Item B
- Item C
[-- Attachment #3: headlink.tex --]
[-- Type: application/x-tex, Size: 845 bytes --]
next prev parent reply other threads:[~2016-12-03 15:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-28 9:03 Bug: Latex export fails with link in headline Scott Otterson
2016-11-28 11:26 ` Nicolas Goaziou
2016-11-29 12:57 ` Scott Otterson
2016-12-03 15:04 ` Scott Otterson [this message]
2016-12-03 21:03 ` Nicolas Goaziou
2016-12-05 8:19 ` Scott Otterson
2016-12-06 11:44 ` 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=CAPY3P0TJRgL3Wn77aFN9QU6Q1+138FHxVcjiTQJRFFA0OkjoEA@mail.gmail.com \
--to=scotto@sharpleaf.org \
--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).