On Friday, September 20, 2013 11:12:37 AM UTC-7, William wrote:
>
> If the problem is the same, you could ask on the ipython list...
> (since sage's command line is ipython).
>
> William
>
> It is. I don't think IPython's prompt configuration looks at the
> environment TERM at all. It's fully
The main thing that's bugging me, actually, is the discrepancy between
notebook and command line.
On the command line:
%runfile /path/to/myfile.sage
In the notebook:
load /path/to/myfile.sage
Note the absence of the %. And neither of these options will work in the
other environment.
--
You
Hi,
What happens if you run straight ipython?
sage -ipython
If the problem is the same, you could ask on the ipython list...
(since sage's command line is ipython).
William
On Fri, Sep 20, 2013 at 10:54 AM, Bill Janssen wrote:
> In an Emacs shell, Sage seems to be ignoring the TERM setting
Hey,
I think you should report this to the gf2x dev as well... you never know.
I've CC'ed Paul Zimmermann in case he cares.
Best,
JP
On Friday, September 20, 2013 3:01:13 PM UTC+2, Andrew Fiori wrote:
>
> This is likely a build error bug on all systems which do not support SSE2
> but where buil
In an Emacs shell, Sage seems to be ignoring the TERM setting (dumb) and
sending ANSI escape sequences to the terminal around the "sage:" prompt.
[pippin:~] wjanssen% printenv TERM
dumb
[pippin:~] wjanssen% /local/sage-5.11/sage
+---
This is likely a build error bug on all systems which do not support SSE2 but
where building is done using the current version of gcc. It may also manifest
as a runtime error on binary builds installed on systems which do not support
SSE2 (but I have not tested that).
I am submitting this here
