Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange behavior in notebook with %octave #1019

Closed
sagetrac-mabshoff mannequin opened this issue Oct 28, 2007 · 6 comments
Closed

strange behavior in notebook with %octave #1019

sagetrac-mabshoff mannequin opened this issue Oct 28, 2007 · 6 comments

Comments

@sagetrac-mabshoff
Copy link
Mannequin

sagetrac-mabshoff mannequin commented Oct 28, 2007

The following was reported by David Galant:

In the notebook, starting a block with '%octave' does not produce a
result.
This has been consistent throughout all releases of sage 2.*
The behavior is consistent on MacOS and Ubuntu Linux.
A sample session showing this is:
 
sage: from math import *
sage: sin(1)
0.8414709848078965
sage: gp.sin(1)
0.8414709848078965066525023216
sage: octave.sin(1)
0.841471
sage: %gp
sage: sin(1)
0.8414709848078965066525023216
sage: %octave
sage: sin(1)
 
sage: 3+2
5
sage: quit
Exited sage process

See http://groups.google.com/group/sage-support/t/273d4045b3f8e14e

Cheers,

Michael

Component: notebook

Issue created by migration from https://trac.sagemath.org/ticket/1019

@sagetrac-mabshoff sagetrac-mabshoff mannequin added this to the sage-2.10.1 milestone Oct 28, 2007
@sagetrac-mabshoff

This comment has been minimized.

@sagetrac-mabshoff sagetrac-mabshoff mannequin changed the title strange behavious in notebook with %octave strange behavior in notebook with %octave Oct 28, 2007
@sagetrac-mabshoff sagetrac-mabshoff mannequin modified the milestones: sage-2.10.1, sage-2.9 Dec 4, 2007
@sagetrac-mabshoff
Copy link
Mannequin Author

sagetrac-mabshoff mannequin commented Feb 15, 2008

comment:3

This is still an issue with 2.10.1 and when I now switch the Sage notebook at sagenb into octave mode it seems like only every second cell is evaluated.

Cheers,

Michael

@boothby boothby assigned williamstein and unassigned boothby Mar 5, 2008
@mwhansen mwhansen assigned mwhansen and unassigned williamstein Sep 3, 2008
@mwhansen
Copy link
Contributor

Attachment: trac_1019.patch.gz

@mwhansen
Copy link
Contributor

comment:6

It turns out that this is caused by the chdir command (which is run before each cell is evaluated) screwing up the syncronization.

This can also be fixed by improving the Octave interface to have better error detection.

@jasongrout
Copy link
Member

comment:7

This works for me. Mike explained the patch and it sounds reasonable. Positive Review.

@sagetrac-mabshoff
Copy link
Mannequin Author

sagetrac-mabshoff mannequin commented Jan 23, 2009

comment:8

Merged in Sage 3.3.alpha1

@sagetrac-mabshoff sagetrac-mabshoff mannequin closed this as completed Jan 23, 2009
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants