emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Martin Butz <mb@mkblog.org>
To: emacs-orgmode@gnu.org
Subject: Re: Upgrade to org 7.9.3.: clock in/out and org-odt export
Date: Wed, 09 Jan 2013 09:06:29 +0100	[thread overview]
Message-ID: <50ED2505.50700@mkblog.org> (raw)
In-Reply-To: <87d2xe53dd.fsf@gmail.com>

Thank you, Bastien and Jabunathan,

as often I failed to answer to the list and sent instead private 
messages back. Sorry for that.

I will try to pinpoint the org-export-problem and deliver some more 
detailed information.

Best
Martin

Am 09.01.2013 06:31, schrieb Jambunathan K:
> Martin Butz <mb@mkblog.org> writes:
>
>> (2) I did some tests with the org-odt-exporter, which where successful
>> in case of a small test file but failed with some of my daily used file.
>> In one case the emacs message buffer seemed to contain the whole export
>> output (pasting just a few lines here)
>
> org-odt.el - The old exporter - hasn't changed much for most of one full
> year.  I wouldn't be surprised, if the problem is elsewhere.
>
> If you can git bisect well and good.
>
>          Or
>
> You can post the BEGINNING of stack trace.  (Your stacktrace doesn't
> seem to be from the beginning).  Btw, it is not clear to me whether you
> are getting a backtrace.
>
>          Or
>
> Try minimal Emacs:  emacs  -L ~/src/org-mode/lisp  -L ~/src/org-mode/contrib/lisp
>
>
> I am willing to address whatever problem that you are seeing.
>


-- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| G. Martin Butz, mb@mkblog.org, 0421 98749324, www.mkblog.org |
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

  reply	other threads:[~2013-01-09  8:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 20:10 Upgrade to org 7.9.3.: clock in/out and org-odt export Martin Butz
2013-01-08 22:48 ` Bastien
2013-01-09  5:31 ` Jambunathan K
2013-01-09  8:06   ` Martin Butz [this message]
2013-01-09 19:25   ` Martin Butz
2013-01-09 20:19     ` Jambunathan K
2013-01-10  9:53       ` Martin Butz

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=50ED2505.50700@mkblog.org \
    --to=mb@mkblog.org \
    --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).