From: Qiang Fang <godblessfq@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug in ox.el
Date: Wed, 13 Sep 2017 16:30:32 +0800 [thread overview]
Message-ID: <CAOHC6G-pVzQn_t8RUyG-jY9vJPeSMGHyO4AMB2oA2T7putv5Ew@mail.gmail.com> (raw)
In-Reply-To: <874ls7kqbp.fsf@delle7240.chemeng.ucl.ac.uk>
The standard version of org has a lot of limitations. Is it possible that the
author of ox-odt gives his repos as a gift to me, and let me deal with the
copyright stuff? I am living in China, a quasi-communist country, :<.
In case you won't check the issue because of it not copy right. The complete bug
report is:
"Lisp nesting exceeds ‘max-lisp-eval-depth’" exceeded, when using
cookies with List Tables.
org-export-table-cell-alignment uses org-export-data to infer cookies of some
columns. I think, it should use other mechanisms like org-element-interpret-data
(may be).
On 9/13/17, Eric S Fraga <esflists@gmail.com> wrote:
> On Wednesday, 13 Sep 2017 at 09:26, Qiang Fang wrote:
>> The original issue is at
>> https://github.com/kjambunathan/org-mode-ox-odt/issues/25
>>
>> "org-export-table-cell-alignment uses org-export-data to infer cookies
>> of some columns. I think, it should use other mechanisms like
>> org-element-interpret-data (may be)."
>>
>> The odt exporter is really useful, it replaces latex in most cases for
>> me. How can I help in getting it into the main org repo?
>>
>
> IIRC, quite some time ago now, there were issues with copyright
> etc. with this particular branch of the ODT exporter. There is an ODT
> exporter in the standard version of org.
>
> --
> : Eric S Fraga via Emacs 26.0.50, Org release_9.0.9-573-g09e612
>
next prev parent reply other threads:[~2017-09-13 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 1:26 Bug in ox.el Qiang Fang
2017-09-13 7:31 ` Eric S Fraga
2017-09-13 8:30 ` Qiang Fang [this message]
2017-09-13 10:38 ` Nicolas Goaziou
2017-09-14 1:35 ` Qiang Fang
2017-09-14 3:53 ` Nick Dokos
2017-09-14 12:57 ` 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=CAOHC6G-pVzQn_t8RUyG-jY9vJPeSMGHyO4AMB2oA2T7putv5Ew@mail.gmail.com \
--to=godblessfq@gmail.com \
--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).