Chris Malone writes:
> Hi,
>
> First off, my =org-mode= is up-to-date - just did a =git pull && make clean
> && make=. Needless to say, the following were an issue before then...
>
> * Question 1:
> Is there a way to force, upon export, an =emacs-lisp= session to be run
> within the current buff
On Mon, Feb 21, 2011 at 12:17 PM, Eric Schulte wrote:
> Chris Malone writes:
>
> > Hi,
> >
> > First off, my =org-mode= is up-to-date - just did a =git pull && make
> clean
> > && make=. Needless to say, the following were an issue before then...
> >
> > * Question 1:
> > Is there a way to force
Chris Malone writes:
[...]
>
> I added =(setq org-confirm-babel-evaluate nil)= to my =.emacs= file, and
> indeed I am not asked about evaluating the code block, but I'm still getting
> the invalid
> syntax error when =org-babel-exp= is called the second time on the
> =emacs-lisp= code block.? I
Hi Eric,
I removed all the compiled elisp files, and the problem still persists.
Next step will be a completely fresh install from git; my current version is
up to date, but maybe there was some conflict that git didn't complain
about...
Chris
On Mon, Feb 21, 2011 at 2:48 PM, Eric Schulte wrote:
Chris Malone writes:
> Hi Eric,
>
> I removed all the compiled elisp files, and the problem still persists.
> Next step will be a completely fresh install from git; my current version is
> up to date, but maybe there was some conflict that git didn't complain
> about...
>
Before doing that could
Ok, this is still perplexing me, as I have a new version from git and I
still get the error. The following is complete list (sorry for the long
email!) of what I have done:
* Get a fresh copy of =org-mode= from git and byte-compile:
#+begin_src: sh
cd ~/install/org-mode
mkdir new_git_clone
Chris Malone writes:
> Ok, this is still perplexing me, as I have a new version from git and I
> still get the error. The following is complete list (sorry for the long
> email!) of what I have done:
>
> * Get a fresh copy of =org-mode= from git and byte-compile:
>
> #+begin_src: sh
> cd ~/ins
On Feb 22, 2011 1:06pm, Eric Schulte wrote:
Chris Malone chris.m.mal...@gmail.com> writes:
> Ok, this is still perplexing me, as I have a new version from git and I
> still get the error. The following is complete list (sorry for the long
> email!) of what I have done:
>
> * Get