On Friday, 10 February 2012 18:06:46 UTC+8, Jonathan Bober wrote: > > By "sage in terminal" I mean "not the notebook." > > In recent builds (maybe mostly in the sage-5.0-beta series, but maybe 4.8, > and maybe older -- I know that's not too helpful) I've occasionally noticed > weird things working with sage from the command line. Sometimes tab > completion has just completely or mostly stopped working until I quit and > restart, and now after hitting CTRL-c I have a terminal where the behavior > of pressing "up" has just changed. > > Normally if I start typing 'G = ', and then hit the up arrow, it will take > me to the previous spot where I started a line this way. (I used to _hate_ > this behavior, and now I can't live without it.) Now, after hitting CTRL-c > in the middle of typing a command (to just erase the whole thing), I find > the behavior has changed, so that when I hit up it just takes me to the > previous line. > > Anyone have any idea what's going on? It's not a big deal, but it seems to > be a strange bug, and annoys me sometimes. >
I have recently noticed this behaviour on MacOSX, especially after resizing the terminal it happens quite a bit. I end up using CTRL-d to delete a symbol in a line, while normally Delete would work. (and when I hit Delete it goes to the next sage: prompt, outputting KeyboardInterrupt) Dima -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
