I wonder why I cannot get a command to abort after
To reproduce this, try some big computation, that will
give you a 200Mb standard basis of an ideal, and then
do dump(":w .....)
and hit ^C.
(or hit ^C in the middle of such a big computation)
Is it because it still wants to finish the command?
I can imagine that commands that modify data in the
memory are hard to abort, but commands like dump, or any
commands that create new objects without destroying old
ones ought to be very cheap (and quick) to abort, IMHO.
PS. the platforms I get this behavour on are Linux and MacosX.
Posted in old Singular Forum on: 2004-12-01 21:48:13+01