emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Unable to export babel results
Date: Mon, 18 Oct 2010 20:48:20 -0700	[thread overview]
Message-ID: <4CBD1504.2020402@gmail.com> (raw)
In-Reply-To: <878w1uhqjb.fsf@gmail.com>

Hi Eric,

On Monday 18 October 2010 07:20 PM, Eric Schulte wrote:
> Hmm,
>
> Are you sure that the version of Org-mode loaded in Emacs is the very
> same version?  What output do you get when you run the org-version
> command?  I get
>
>    Org-mode version 7.01trans (release_7.01h.747.g57e7)
>

I just updated to the master HEAD, still no luck. Before and after
updating I get this, "Org-mode version 7.01trans". I don't know why I
have never seen the part within the parentheses before.

> It is common for people to have a local checkout of the latest version
> of org-mode, but still have an older version located somewhere in their
> site-lisp directory loaded overtop of the new checkout.  If this is the
> case you may need to tweak your classpaths.
>
> If you are using the latest version of Org-mode, then I'm not sure what
> the problem could be.  I've exported your attached example file with
> org-confirm-babel-evaluate set to both nil and to true, in both cases it
> worked for me without problem.  Are you on a windows box (another one of
> my go-to potential culprits)?
>

I use "GNU Emacs 24.0.50.1 (2010-10-15)" on Fedora 13. To install 
org-mode, I overwrite the default emacs org directory,

$EMACS_INSTALL_PATH/share/emacs/24.0.50/lisp/org

I know this works because after I update emacs, `org-version' returns 
"7.01h" and subsequently updating org-mode changes the version as I 
stated above. Do you think I might have mixed version of files? I used 
to install it under,

$EMACS_INSTALL_PATH/share/emacs/site-lisp

but I prefer having things all organised inside a directory and I am not 
confident enough to write my own site-lisp file.

FWIW, I have this same issue on a similar Ubuntu 10.04 installation of 
Emacs 24 and org-mode HEAD.

> Best -- Eric

Thanks a lot for looking into this.

-- 
Suvayu

Open source is the future. It sets us free.

  reply	other threads:[~2010-10-19  3:48 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-18  4:31 Unable to export babel results suvayu ali
2010-10-19  1:15 ` Eric Schulte
2010-10-19  2:02   ` suvayu ali
2010-10-19  2:20     ` Eric Schulte
2010-10-19  3:48       ` Suvayu Ali [this message]
2010-10-19 13:36         ` Eric Schulte
2010-10-19 17:46           ` Suvayu Ali
2010-10-19 17:54             ` Eric Schulte
2010-10-19 18:24               ` Nick Dokos
2010-10-19 19:37                 ` Suvayu Ali
2010-10-19 21:36                   ` Nick Dokos
2010-10-19 21:52                     ` suvayu ali
2010-10-19 17:37         ` Achim Gratz
2010-10-19 17:52           ` suvayu ali

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=4CBD1504.2020402@gmail.com \
    --to=fatkasuvayu+linux@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=schulte.eric@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).