From: tsd@tsdye.com (Thomas S. Dye)
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Fwd: Re: Bug? in texinfo exporter
Date: Sun, 10 Feb 2013 17:19:27 -1000 [thread overview]
Message-ID: <m1ip5zbkqo.fsf@tsdye.com> (raw)
In-Reply-To: <CAEWDx5cEbM2n0iBQEj6aHb+ahyxwUr=h3f8KR_vJ9LsyQ3+5Kg@mail.gmail.com> (Jonathan Leech-Pepin's message of "Sat, 9 Feb 2013 18:00:46 -0500")
Aloha Jon,
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> ---------- Forwarded message ----------
> From: "Jonathan Leech-Pepin" <jonathan.leechpepin@gmail.com>
> Date: Feb 9, 2013 8:57 AM
> Subject: Re: [O] Bug? in texinfo exporter
> To: "Thomas S. Dye" <tsd@tsdye.com>
> Cc:
> Just realized I hit reply not reply-all
>
> If Nick's fix fixes it do much the better.com but I'm pretty sure the comma
> isn't the culprit.
Yes, I believe you are right. The commas are not the culprits.
Apologies for the red herring.
Perhaps Nicolas should revert the commit? Could you check if this is
the right thing to do?
I *have* found a bug/limitation of the texinfo exporter. If a link is
split between two lines the exporter doesn't handle it correctly. A
split link is exported like @ref{A-split-link}, when it should be @ref{A
split link}, I think.
If this is a limitation, please let me know so I can put all the links
on one line.
All the best,
Tom
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2013-02-11 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 3:11 Bug? in texinfo exporter Thomas S. Dye
2013-02-09 18:31 ` Nicolas Goaziou
[not found] ` <CAEWDx5dLyC0xmOdBy8aO7N932cbV_h+UN7rx_qw-h6JZ+3i7vQ@mail.gmail.com>
2013-02-09 23:00 ` Fwd: " Jonathan Leech-Pepin
2013-02-11 3:19 ` Thomas S. Dye [this message]
2013-02-11 6:59 ` Nicolas Goaziou
2013-02-11 12:08 ` Jonathan Leech-Pepin
2013-02-13 7:44 ` Nicolas Goaziou
2013-02-11 18:59 ` Thomas S. Dye
2013-02-13 7:45 ` Nicolas Goaziou
2013-02-13 16:09 ` Thomas S. Dye
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=m1ip5zbkqo.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@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).