C-c does not work as expected

[Thomas Kahle <thomas.kahle@…>]

When pressing C-c in a lenghty computation I get

abort command(a), continue(c) or quit Singular(q) ?

when pressing (a), the computation just continues.

This is also Gentoo bug 403063 ( ​https://bugs.gentoo.org/show_bug.cgi?id=403063 )

Thanks!

[dreyer]

I think, this is a misunderstanding: the lengthy computation is probably a sequence of several commands (in most cases it is). Aborting the first of them does not prevent the next 99 to run.

[Thomas Kahle <thomas.kahle@…>]

Replying to dreyer:

I think, this is a misunderstanding: the lengthy computation is probably a sequence of several commands (in most cases it is). Aborting the first of them does not prevent the next 99 to run.

For me it also applies to single commands, e.g. 'std'.

[hannes]

Wrong: "abort" means here that the current kernel command continues and the interpreter then aborts. In the example with the 100 several commands: the current one will be completed, all the other will not run.

To abort a kernel command, type "r", which is undocuments for a good reason: It does a longjump to the interpreter and does not clean up: very bad things(TM) may happen.

[dreyer]

Sorry for the confusion: I meant CPU commands, i.e. those 99 steps within a single kernel command (including clean-up etc.), Meanwhile, Hans explained it accordingly.

[Thomas Kahle <thomas.kahle@…>]

Alright, so now we know what's going on. How hard would it be to implement the right thing(TM). Could the interpreter return to the state before the last command was issued within a reasonable time-frame (<5 seconds, say)?

[hannes]

solved with rev. 655fe5d