From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: Tomas Grigera <tgrigera@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: Problem (bug?) evaluating octave code ("function name does not agree with file name)
Date: Tue, 18 Aug 2015 20:38:48 +0100 [thread overview]
Message-ID: <87mvxol73r.fsf@ucl.ac.uk> (raw)
In-Reply-To: <CAJMNdQKk8qgBr70L=grFo6sg_z7B1oEEPVjNuPD9iTYF0MnsyA@mail.gmail.com> (Tomas Grigera's message of "Tue, 18 Aug 2015 10:42:11 -0300")
On Tuesday, 18 Aug 2015 at 10:42, Tomas Grigera wrote:
> Hello list,
>
> I am a very happy user of orgmode and babel. I recently picked up a
> document from last year, and found that code blocks that used to
> evaluate fine now don't. A code block like this
[...]
> There has been some change, of which I am unaware, in the way babel
> handles this block that leads to this behaviour. However, it seems to
> me that it is a well-formed block and should evaluate fine. Am I
> wrong?
Just to confirm that you are not wrong and I ran into this a while ago
now. That is, problems with functions defined in the middle of the code
as opposed to functions in their own .m files. I didn't have time to
figure out what was wrong at the time due to deadlines so found other
ways of doing what I wanted including @(x) function definitions.
The strange thing is that babel seems to not leave any code in the /tmp
files it creates so I cannot see what code org babel is trying to execute.
--
: Eric S Fraga (0xFFFCF67D), Emacs 25.0.50.2, Org release_8.3.1-117-gc98729
next prev parent reply other threads:[~2015-08-18 19:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 13:42 Problem (bug?) evaluating octave code ("function name does not agree with file name) Tomas Grigera
2015-08-18 19:38 ` Eric S Fraga [this message]
2015-08-18 21:10 ` Tomas Grigera
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=87mvxol73r.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tgrigera@gmail.com \
/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).