> >> >> > >> > F test-ob-exp/org-babel-exp-src-blocks/w-no-file >> > Testing export from buffers which are not visiting any file. >> > (wrong-type-argument stringp nil) >> > >> > F test-ob-exp/org-babel-exp-src-blocks/w-no-headers >> > Testing export without any headlines in the org-mode file. >> > (wrong-type-argument stringp nil) >> > >> > F test-ob-lob/export-lob-lines >> > Test the export of a variety of library babel call lines. >> > (wrong-type-argument stringp nil) >> > >> >> I have no idea what could be going wrong with these executions, would it >> be difficult to generate backtraces for these failures? > > No, its really easy (as expected w/ Emacs): Section on interactive > debugging ERT mentions "b" to create the backtrace. > > In case of w-no-file and w-no-headers `org-todo-line-regexp' is bound > to nil, in export-lob-lines `org-maybe-keyword-time-regexp' is bound > to nil. Backtraces are attached. >
So, Could it be that for some reason using Emacs22 all variable whose values are set in `org-set-regexps-and-options' immediately following ;; Compute the regular expressions and other local variables in org.el are somehow not having their values set? I assume that Org-mode simply wouldn't work on Emacs22 if this was generally the case, so could there be something about the way that you are loading Org-mode? Maybe explicitly adding a call to this function to the Emacs22 configuration would fix these test errors? Hope this is helpful, please let me know if I'm miss understanding the test results. Thanks -- Eric > > Best, > -- David > -- > OpenPGP... 0x99ADB83B5A4478E6 > Jabber.... dmj...@jabber.org > Email..... dm...@ictsoc.de > > > -- Eric Schulte http://cs.unm.edu/~eschulte/