I confirm that with Debian's Emacs, org-babel works well after the (require 'tramp-cache): GNU Emacs 24.3.1 (x86_64-pc-linux-gnu, GTK+ Version 3.12.2) of 2014-06-06 on barber, modified by Debian
But it fails with my compiled one from 2014-06-20. So is it because of tramp-cache or org-babel? On Fri, Jun 27, 2014 at 12:19 AM, Daniel Clemente <n142...@gmail.com> wrote: > > El Thu, 26 Jun 2014 12:36:47 -0400 Eric Schulte va escriure: > > > #+BEGIN_SRC python :results output > > > print "x" > > > #+END_SRC > > > > > > It prints: > > > > > > #+RESULTS: > > > : None > > > > > > I expected to see "x". This worked some days ago. > > > > > > > This works for me using the latest version of Org-mode with an Emacs > > launched by running "make vanilla" from the base of the Org-mode repo. > > > I didn't know "make vanilla". It worked fine from there, I don't know > why from "emacs -Q" it didn't. > > > Maybe the problem is in your configuration? > > Exactly, it is from my configuration, because after loading my full > configuration, I see the problem again and code highlighting suddenly > disappears. > > I identified the exact lines that cause org-babel to stop failing. > Bewonder: > > (autoload 'tramp "tramp" "Remotely access files." t) > (require 'tramp-cache) > > Yes! After C-x C-e on the first line, org-babel still works. After C-x > C-e on the second line, it doesn't work anymore. > There were some Tramp changes in latest Emacs, maybe they are bad. I'm > using: GNU Emacs 24.4.50.1 (x86_64-unknown-linux-gnu, X toolkit, Xaw > scroll bars) of 2014-06-20 on la4 > > > What a strange bug... > >
