Opened 8 years ago

Closed 8 years ago

#725 closed proposed feature (fixed)

Interrupt option to just return to prompt

Reported by: jdemeyer@… Owned by: somebody
Priority: minor Milestone: 3-2-0 and higher
Component: dontKnow Version: 3-1-7
Keywords: cntrlc, interrupt Cc:


(Context: we are working in Sage to improve interrupting in Singular, but it's made difficult because Singular is so unpredictable w.r.t. interrupts)

First of all, it's not at all clear to me what the various options actually mean:

abort after this command(a), abort immediately(r), print backtrace(b), continue(c) or quit Singular(q) ?

I don't understand what the a and r options mean.

Secondly, what I'm missing is an option "forget whatever you are doing and return immediately to the Singular prompt".

Change History (1)

comment:1 Changed 8 years ago by hannes

Resolution: fixed
Status: newclosed

a: abort after the current kernel command and return to the Singular prompt

r: longjump to the Singular interpreter, may not work (i.e. resulting in a crash) depending on libc/compiler/etc.- should (normally) not used

"forget whatever you are doing and return immediately to the Singular prompt": use option a which returns as soon as possible, but keeps all data.(Interrupting a kernel command is not supported) If you want a clean session, start a new Singular process.

Note: See TracTickets for help on using tickets.