emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Price <moptop99@gmail.com>
To: Jambunathan K <kjambunathan@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-odt list bug - help reproducing?
Date: Fri, 12 Nov 2010 07:10:04 -0500	[thread overview]
Message-ID: <AANLkTiku+Lv4A0sMA+9mRwi8iLikoyW287SATn9BK9W2@mail.gmail.com> (raw)

[-- Attachment #1.1: Type: text/plain, Size: 893 bytes --]

On Wed, Nov 10, 2010 at 11:14 AM, Jambunathan K <kjambunathan@gmail.com>wrote:

> Matt
> I am unable to reproduce the said behaviour.
> From my work-area (which is same as that in git), the odt produced is
> valid. I am attaching the odts produced in my work area. Let me know if
> what is attached is not what you expect.

I wonder if anyone on the list can reproduce the bug I'm finding in
Jambunathan's odt exporter?   The attached org file creates the attached
invalid odt file for me -- this is true both on my main laptop and in a
clean environment I just went to some trouble to create on another computer,
but J cannot reproduce the error.  I'm wondering if perhaps there's some
implicit dependency in J's code somewhere that neither of us sees, and that
isn't fulfilled on either of my systems.  I can't think of any other

thanks as  always for your help!

[-- Attachment #1.2: Type: text/html, Size: 1251 bytes --]

[-- Attachment #2: desc_test_short1.odt --]
[-- Type: application/zip, Size: 7080 bytes --]

[-- Attachment #3: desc_test_short_2.odt --]
[-- Type: application/vnd.oasis.opendocument.text, Size: 7176 bytes --]

[-- Attachment #4: Type: text/plain, Size: 201 bytes --]

Emacs-orgmode mailing list
Please use `Reply All' to send replies to the list.

             reply	other threads:[~2010-11-12 12:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-12 12:10 Matt Price [this message]
2010-11-12 12:43 ` org-odt list bug - help reproducing? Matt Price
2010-11-12 20:51 ` Jambunathan K
2010-11-12 21:36   ` Matt Price

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:

  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=AANLkTiku+Lv4A0sMA+9mRwi8iLikoyW287SATn9BK9W2@mail.gmail.com \
    --to=moptop99@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kjambunathan@gmail.com \


* 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


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).