From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com>
Cc: Org Mode Mailing List <emacs-orgmode@gnu.org>,
"Thomas S. Dye" <tsd@tsdye.com>
Subject: Re: Fwd: Re: Bug? in texinfo exporter
Date: Wed, 13 Feb 2013 08:44:16 +0100 [thread overview]
Message-ID: <87621waca7.fsf@gmail.com> (raw)
In-Reply-To: <CAEWDx5cTcJBCytoEDfTYBQoSsphdLDBEwc_wG_M2JMrGwEsNRQ@mail.gmail.com> (Jonathan Leech-Pepin's message of "Mon, 11 Feb 2013 07:08:33 -0500")
Jonathan Leech-Pepin <jonathan.leechpepin@gmail.com> writes:
> On Feb 11, 2013 1:59 AM, "Nicolas Goaziou" <n.goaziou@gmail.com> wrote:
>>
>> tsd@tsdye.com (Thomas S. Dye) writes:
>>
>> > Aloha Jon,
>>
>> [...]
>>
>> > 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?
>>
>> My fix isn't about the comma. Didn't it work?
>>
>
> Your fix seems to have worked from what I can see (it was what I was
> thinking of fixing at least). The comma was Tom's initial guess.
Actually, an `org-export-solidify-link-text' may be needed (along with
the receiver part of the link), in case one of the properties that were
previously transcoded contains a forbidden character. I let you decide
about it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-13 7:44 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
2013-02-11 6:59 ` Nicolas Goaziou
2013-02-11 12:08 ` Jonathan Leech-Pepin
2013-02-13 7:44 ` Nicolas Goaziou [this message]
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=87621waca7.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jonathan.leechpepin@gmail.com \
--cc=tsd@tsdye.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).