Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Recently, in ipython5.0 branch of https://github.com/stakemori/sage-shell-mode, I implemented functions for some of ANSI sequences. (sage-shell-mode handles only ^[[nA, ^[[nB, ^[[nC, ^[[nD, ^[[nH and ^[[nJ) It is not stable enough yet, but it works. I think a similar fix also works for

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Am Donnerstag, 18. August 2016 13:33:41 UTC+2 schrieb Volker Braun: > > PS: It would be easy enough to expose the simple-prompt either to the sage > command line or have a special sage-embedded commandline entrypoint that > starts witout any ANSI sequences. > > I have absolutely no idea how to

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

PS: It would be easy enough to expose the simple-prompt either to the sage command line or have a special sage-embedded commandline entrypoint that starts witout any ANSI sequences. On Thursday, August 18, 2016 at 1:32:18 PM UTC+2, Volker Braun wrote: > > IMHO this is an intentional upstream

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

IMHO this is an intentional upstream change and not a bug. So we'll have to either go with it or fork our own IPython. And I don't want to maintain an IPython fork. On Thursday, August 18, 2016 at 11:08:41 AM UTC+2, Martin R wrote: > > Since solving this appears to be tricky, is there a way to

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Since solving this appears to be tricky, is there a way to undo the ipython-5 thing? (I'd like to keep other things from sage 7.4... -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

> On Aug 14, 2016, at 11:28 AM, Johan S. H. Rosenkilde > wrote: > > Hi, > > On my machine, Ivan's workaround also does not help: I get exactly the > same behaviour as Martin R. I run Emacs 24.5.1 on Arch Linux 4.6.3-1, > x86_64. > > See also this depressing post on

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Hi, On my machine, Ivan's workaround also does not help: I get exactly the same behaviour as Martin R. I run Emacs 24.5.1 on Arch Linux 4.6.3-1, x86_64. See also this depressing post on Emacs Stack Exchange: http://emacs.stackexchange.com/questions/24453/weird-shell-output-when-using-ipython-5

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

I tried %config SageTerminalInteractiveShell.simple_prompt=True in a running session inside Emacs, but it didn’t help. Perhaps it has to be done at the command line? -Ivan > On Aug 14, 2016, at 1:54 AM, Volker Braun wrote: > > Ipython 5 has now a comman-line switch

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

On Aug 14, 2016 11:26 AM, "'Martin R' via sage-devel" < sage-devel@googlegroups.com> wrote: > > Can't we undo the ipython 5 thing? It's a major nuisance on the command line, too. > +1 I find the new coloration in the Sage command line in the beta release quite extreme and nearly unreadable in

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

at least on my other computer, running GNU Emacs 24.4.1 (x86_64-pc-linux-gnu, GTK+ Version 3.14.9) of 2015-03-21 on kissel, modified by Debian this does not help. However, on this computer I don't even get to the (weird) sage prompt, unless I hit C-g. I evaluated the two definitions you

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

Ipython 5 has now a comman-line switch "ipython --simple-prompt" that disables all escape sequences, but also disables prompt customizations. So instead of sage: its then always In[] / Out[]. I didn't find a way to turn of all ansi sequences while still changing the prompt to "sage:". On

Re: [sage-devel] sage_mode for emacs has display problem in sage 7.4 beta0

It looks like ipython is printing invalid (or at least unknown to Emacs) I got it to ignore them by setting (setq ansi-color-drop-regexp " \\[\\([ABCDsuK]\\|[12][JK]\\|=[0-9]+[hI]\\|[0-9;]*[HfDnC]\\|\\?[0-9]+[hl]\\|J\\)") There is also a bug in my version of Emacs which causes these