Thomas S. Dye <t...@tsdye.com> wrote: > ... > I did hit on a revision that was neither good nor bad: > > commit 8562273b272024a630a582b0e1b94c481d8abeec > Author: Eric Schulte <schulte.e...@gmail.com> > Date: Sat Oct 16 13:21:47 2010 -0600 > > ob-ref: don't forget arguments to referenced code blocks > > * lisp/ob-ref.el (org-babel-ref-resolve): bringing the referent > arguments back to their params before evaluation > > This one puts these lines in *Messages* when I export to LaTeX > > executing Org code block... > if: Symbol's value as variable is void: result-type >
Yeah, that was the error that stopped me cold as well, although I hit it on a different commit (I think) - there must be a way to get around the problem but it certainly makes things more difficult. I imagine the way to go is to find a commit before this error was introduced and a commit after it was fixed and try those with your problem: it might allow you to bypass the problematic range (in which case, you might be able to continue bisecting all the way to the end), or it might limit the bad commit to this range - the latter is still valuable to know but certainly not as definitive as "this is the bad commit". And in any case, all of this would fall into the "advanced" appendix in the git bisection book. Sorry it didn't pan out but I hope that you had fun digging, Nick _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
