From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lawrence Bottorff Subject: Re: Scheme code block gives false error message Date: Mon, 14 Sep 2015 03:50:38 +0000 Message-ID: References: <877fnuj2q4.fsf@pierrot.dokosmarshall.org> <87y4gagkxc.fsf@pierrot.dokosmarshall.org> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e013d1926fa3e1a051facf7a5 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46411) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbKmv-0006Uy-E0 for emacs-orgmode@gnu.org; Sun, 13 Sep 2015 23:50:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZbKmt-0003xj-Vu for emacs-orgmode@gnu.org; Sun, 13 Sep 2015 23:50:41 -0400 Received: from mail-la0-x22a.google.com ([2a00:1450:4010:c03::22a]:32919) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZbKmt-0003xA-Gb for emacs-orgmode@gnu.org; Sun, 13 Sep 2015 23:50:39 -0400 Received: by lamp12 with SMTP id p12so77840353lam.0 for ; Sun, 13 Sep 2015 20:50:38 -0700 (PDT) In-Reply-To: <87y4gagkxc.fsf@pierrot.dokosmarshall.org> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org --089e013d1926fa3e1a051facf7a5 Content-Type: text/plain; charset=UTF-8 I think this ( https://mobiusengineering.wordpress.com/2015/01/11/using-emacs-org-with-mit-scheme/) describes my problem. Basically, it's with ob-scheme.el. The article seems to say that my problem is scheme stuff being handled improperly by the elisp of ob-scheme.el. I'll try his workaround and see if it works. He also seems to believe Scheme is a second-class citizen in babel-land. On Sun, Sep 13, 2015 at 7:48 PM, Nick Dokos wrote: > Lawrence Bottorff writes: > > > Sorry, Nick, not following you. Could you elaborate more? As a rank > > beginner, I'm not sure what a backtrace is or how to produce one or > > how it read it. What do you mean by "master" and "maint"? > > > > It's a debugging aid: it's a dump of the call stack at the time of the > error. It tells you how you got there. > > See > > (info "(org) Feedback") > > on how to enable it and produce a useful backtrace. > > You read it from bottom to top: the bottom-most function has called > the next-to-bottom-most function, ..., which has called the top-most > function, which is in the middle of evaluating some expression when > the error occurred. The section on Debugging in the Emacs Lisp manual > contains more information. > > Re: "master" and "maint" - I didn't know which version of org you were > using, so I tried it with both the master branch and the maint branch of > the git tree, as they were yesterday. I should probably have provided > more explicit versions but it was late and I was tired. > > For the record, at the time that I was doing that: > > "master" was Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @ > /home/nick/elisp/org-mode/lisp/) > "maint" was Org-mode version 8.3.1 (release_8.3.1-120-gbc322f @ > /home/nick/elisp/org-mode/lisp/) > > HTH > -- > Nick > > > --089e013d1926fa3e1a051facf7a5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I think this (https://mobiusengineeri= ng.wordpress.com/2015/01/11/using-emacs-org-with-mit-scheme/) describes= my problem. Basically, it's with ob-scheme.el. The article seems to sa= y that my problem is scheme stuff being handled improperly by the elisp of = ob-scheme.el. I'll try his workaround and see if it works. He also seem= s to believe Scheme is a second-class citizen in babel-land.

On Sun, Sep 13, 2015 at 7:= 48 PM, Nick Dokos <ndokos@gmail.com> wrote:
Lawrence Bottorff <borgauf@gmail.com> writes:

> Sorry, Nick, not following you. Could you elaborate more? As a rank > beginner, I'm not sure what a backtrace is or how to produce one o= r
> how it read it. What do you mean by "master" and "maint= "?
>

It's a debugging aid: it's a dump of the call stack at the t= ime of the
error. It tells you how you got there.

See

=C2=A0 (info "(org) Feedback")

on how to enable it and produce a useful backtrace.

You read it from bottom to top: the bottom-most function has called
the next-to-bottom-most function, ..., which has called the top-most
function, which is in the middle of evaluating some expression when
the error occurred. The section on Debugging in the Emacs Lisp manual
contains more information.

Re: "master" and "maint" - I didn't know which vers= ion of org you were
using, so I tried it with both the master branch and the maint branch of the git tree, as they were yesterday. I should probably have provided
more explicit versions but it was late and I was tired.

For the record, at the time that I was doing that:

"master" was Org-mode version 8.3.1 (release_8.3.1-234-g8c85c9 @<= br> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/home/nick/elisp/org-mode/l= isp/)
"maint"=C2=A0 was Org-mode version 8.3.1 (release_8.3.1-120-gbc32= 2f @
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/home/nick/elisp/org-mode/l= isp/)

HTH
--
Nick



--089e013d1926fa3e1a051facf7a5--