From: Carsten Dominik <carsten.dominik@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: return of problem with hyperlinks in verbatim code when exporting to latex
Date: Tue, 2 Feb 2010 06:32:42 +0100 [thread overview]
Message-ID: <1F9F5D89-F150-401D-B1B0-6BD0A57B59F8@gmail.com> (raw)
In-Reply-To: <87tyu0trid.wl%ucecesf@ucl.ac.uk>
Fixed, thanks.
- Carsten
On Feb 2, 2010, at 1:23 AM, Eric S Fraga wrote:
> At Mon, 01 Feb 2010 23:58:16 +0000,
> Eric S Fraga wrote:
>>
>> [1 <text/plain; US-ASCII (7bit)>]
>> Carsten,
>>
>> possibly the recent changes to org-mode for how external links are
>> handled in the latex export (if I remember some of the messages
>> flying
>> by in the past week or so correctly) may have re-introduced a bug
>> that
>> existed a couple of months ago. Specifically, in some circumstances,
>> the appearance of "[[" in a verbatim code segment is translated into
>> \hyperref upon export to latex.
>
>
> The puzzle deepens. Please see attached files which show one case not
> working and the other working just fine (in the same file) with the
> only difference between them (as far as I can see but it *is* late at
> night now...) being a single space. I've hopefully managed to protect
> the file from any email system mangling along the way...
>
> I'm off to bed as my brain is turning into mush ;-)
>
> Thanks again,
> eric
> <
> examplebug
> .org><examplebug.pdf>_______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
- Carsten
next prev parent reply other threads:[~2010-02-02 5:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 23:58 return of problem with hyperlinks in verbatim code when exporting to latex Eric S Fraga
2010-02-02 0:23 ` Eric S Fraga
2010-02-02 5:32 ` Carsten Dominik [this message]
2010-02-02 7:57 ` Eric S Fraga
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=1F9F5D89-F150-401D-B1B0-6BD0A57B59F8@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).