From: Lawrence Bottorff <borgauf@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Scheme code block gives false error message
Date: Mon, 14 Sep 2015 03:50:38 +0000 [thread overview]
Message-ID: <CAFAhFSXZxmWaXppuhNb2yAGWO6BX_2S0CUn0u1hycP0bsk8CbQ@mail.gmail.com> (raw)
In-Reply-To: <87y4gagkxc.fsf@pierrot.dokosmarshall.org>
[-- Attachment #1: Type: text/plain, Size: 1836 bytes --]
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 <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 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
>
>
>
[-- Attachment #2: Type: text/html, Size: 2597 bytes --]
next prev parent reply other threads:[~2015-09-14 3:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-12 1:23 Scheme code block gives false error message Lawrence Bottorff
2015-09-13 4:03 ` Lawrence Bottorff
2015-09-13 5:41 ` Nick Dokos
2015-09-13 13:14 ` Lawrence Bottorff
2015-09-13 19:48 ` Nick Dokos
2015-09-14 3:50 ` Lawrence Bottorff [this message]
2015-09-14 13:39 ` Nick Dokos
2015-09-14 15:56 ` Lawrence Bottorff
2015-09-14 18:55 ` Nick Dokos
2015-09-14 21:18 ` Lawrence Bottorff
2015-09-15 1:38 ` Nick Dokos
2015-09-15 3:10 ` Nick Dokos
2015-09-15 4:41 ` Nick Dokos
2015-09-15 4:48 ` Nick Dokos
2015-09-15 17:08 ` Lawrence Bottorff
2015-09-15 17:25 ` Lawrence Bottorff
2015-09-15 18:54 ` Lawrence Bottorff
2015-09-15 19:14 ` Nick Dokos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFAhFSXZxmWaXppuhNb2yAGWO6BX_2S0CUn0u1hycP0bsk8CbQ@mail.gmail.com \
--to=borgauf@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).