From: Jambunathan K <kjambunathan@gmail.com>
To: Wiskey 5 Alpha <wiskey5alpha@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Publishing org project as odt
Date: Sat, 22 Dec 2012 23:41:53 +0530 [thread overview]
Message-ID: <87obhmufbq.fsf@gmail.com> (raw)
In-Reply-To: <50D5F3AC.1090805@gmail.com> (Wiskey's message of "Sat, 22 Dec 2012 12:53:48 -0500")
Wiskey 5 Alpha <wiskey5alpha@gmail.com> writes:
> On 12/22/2012 07:54 AM, Jambunathan K wrote:
>> Wiskey 5 Alpha <wiskey5alpha@gmail.com> writes:
>>
>>> Hello,
>>> I have a rather large project that I currently export to odt
>>> files. I tried the org-export-as-odt-batch command line function but
>>> it fails,
>>
>> Can you tell how it fails. In your init file (the one used by batch
>> emacs), you can put
>>
>> (setq debug-on-error t)
>>
>> to get a stack trace or some such info.
>>
>>> and subsequently deletes all files in the directory.
>>
>> Deletes what files?
> I guess technically , it doesn't delete them, but they are zipped into
> the .odt file, and not present in the directory...
True. The .org file - I believe everything in the work dir - goes in to
the ZIP file. So it is in the ZIP file.
But when a file is lost, panic ensues and brain stops working.
--
next prev parent reply other threads:[~2012-12-22 18:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-21 18:42 Publishing org project as odt Wiskey 5 Alpha
2012-12-22 12:54 ` Jambunathan K
2012-12-22 16:01 ` Wiskey 5 Alpha
2012-12-22 17:57 ` org-odt: Batch exports creates data loss, deletes original org file Jambunathan K
2012-12-22 17:58 ` Jambunathan K
2012-12-23 7:29 ` bug#13254: " Jambunathan K
2012-12-23 7:29 ` Jambunathan K
[not found] ` <87k3s9w7ij.fsf@gmail.com>
2012-12-23 11:47 ` Bastien
2013-01-03 6:43 ` Glenn Morris
2013-01-03 9:15 ` Bastien
2012-12-22 17:32 ` Publishing org project as odt Wiskey 5 Alpha
2012-12-22 17:53 ` Wiskey 5 Alpha
2012-12-22 18:11 ` Jambunathan K [this message]
2012-12-22 18:46 ` Wiskey 5 Alpha
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=87obhmufbq.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wiskey5alpha@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).