[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] Problem (bug?) evaluating octave code ("function name does not a

From: Tomas Grigera
Subject: Re: [O] Problem (bug?) evaluating octave code ("function name does not agree with file name)
Date: Tue, 18 Aug 2015 18:10:08 -0300

Thanks Eric,

My workaround was to use :session, though not completely satisfactory
(I need to clean up the output).

Your comment made me notice

1. octave reports the problem filename as empty
2. the undefined function call happens at 'line 1', which would not be
the case if the whole code block was copied to a file.

It seems babel is feeding octave the lines one-by-one.  Strange.


On Tue, Aug 18, 2015 at 4:38 PM, Eric S Fraga <address@hidden> wrote:
> 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, Org release_8.3.1-117-gc98729

reply via email to

[Prev in Thread] Current Thread [Next in Thread]