Tag Info

3

The difference is the following: When you call Quit[] as input in a notebook, then the front end sends this command over the main MathLink connection to the Kernel like any other input. If you are already evaluating a long-running (or hanging) command, the Kernel won't quit because (as Alexey already pointed out) the quit command is queued and waits until ...

1

The following is a slightly simplified version of your DynamicModule: DynamicModule[{x}, Column[{Button["start", x = 0; RunScheduledTask[x++;, {1, 5}]], Row[{Dynamic[HoldForm[x]], " = ", Dynamic[x]}]}] ] When you evaluate this for the first time, underneath the button you see the output (* FEx$$82 = FEx$$82 *) (very likely with a different ...

8

You cannot Quit kernel while evaluation is still running: the Quit[] command will be placed in the queue and executed only after finishing of evaluation of all the previous inputs. In contrast, Evaluation>>Quit Kernel will quit the kernel immediately even if it is still running. UPDATE As Kuba notice in the comments, via "Preemptive" link it is ...

0

It is only a workaround, but I found a way which works reproducible: I start Mathematica merely with mathematica -cleanstart. Whenever the in the question mentioned behavior occurs, I exit Mathematica, restart and open a .nb which contains only the line titanic = ExampleData[{"Dataset", "Titanic"}] After evaluation of this example, I'm able to evaluate ...

Top 50 recent answers are included