after aborting a running script or macro (with abort or other), console print not working
Reported by Jakub Kopac
reaktor_test.sce (2.17 KB, text/plain)
RUN THIS CODE
BUG DESCRIPTION:
----------------
after run of test code no calculation is printed in console
ERROR LOG:
----------
NONE
HOW TO REPRODUCE THE BUG:
-------------------------
run attached script, then try to calculate in console (e.g. 3/28)
OTHER INFORMATION:
------------------Activity
assigned to @mottelet
added 6.0.1 Bugzilla Desktop - workspace Medium labels
By Stéphane MOTTELET (@mottelet)
A minimal example of a code producing the same problem is a a script with the following line:
abort
Typing "abort" on the command line won't break the display of expression result, but running a script containing "abort" will.
-
By Samuel GOUGEON (@sgougeon)
[@Stéphane: i agree and reset to Console the initial component set by Jakub. The components are being redefined, but till it is not yet done, "Internal" should be avoided because it is not at all specific. It is a bag for overall contents. All is internal, except Java, TCL, and thirdparties stuff... So as it is presently defined, this "Internal" component means nothing. Here, the issue is clearly about display in the Console, linked to abort and mode(). BTW, the categorization should be on the users and usages point of view, not on the development/analyzing/fixing one, unless it impacts features for several clearly distinct components.]
-
By Stéphane MOTTELET (@mottelet)
ok.
-
By Stéphane MOTTELET (@mottelet)
*** #15916 (closed) has been marked as a duplicate of this bug. ***
-
By Stéphane MOTTELET (@mottelet)
The problem occurs when the script is run in mode(-1), typically when clicking the "Execute" button of SciNotes or typing exec("script.sce",-1). By default Scilab starts in mode(2) but after executing a simple script with "abort" mode() is -1:
--> disp(mode())
--> mputl('abort',TMPDIR+"/tmp.sce");
--> exec(TMPDIR+"/tmp.sce",-1) --> disp(mode())
-1.
-
By Stéphane MOTTELET (@mottelet)
The problem occurs when the script is run in mode(-1), typically when clicking the "Execute" button of SciNotes or typing exec("script.sce",-1). By default Scilab starts in mode(2) but after executing a simple script with "abort" mode() is -1:
--> disp(mode())
--> mputl('abort',TMPDIR+"/tmp.sce");
--> exec(TMPDIR+"/tmp.sce",-1) --> disp(mode())
-1.
-
By Stéphane MOTTELET (@mottelet)
Fix under review @ https://gitlab.com/scilab/legacy_codereview/-/wikis/changes/20678/
-
By Stéphane MOTTELET (@mottelet)
(In reply to Hugo Veuillez from comment #8)
Thank you, when is planned the next release ? (I guess 6.0.2)
February, likely
Is there an "easy" way to install the correction before this ?
No. But on the meantime you can insert mode(2) or mode(0) before « abort »
-
By Samuel GOUGEON (@sgougeon)
(In reply to Hugo Veuillez from comment #8)
Thank you, when is planned the next release ? (I guess 6.0.2) Is there an "easy" way to install the correction before this release?
Yes, it will be included in all continuously built releases after it is merged: https://build.scilab.org/view/Scilab%206.0/
-
By Stéphane MOTTELET (@mottelet)
(In reply to Samuel GOUGEON from comment #10)
(In reply to Hugo Veuillez from comment #8)
Thank you, when is planned the next release ? (I guess 6.0.2) Is there an "easy" way to install the correction before this release?
Yes, it will be included in all continuously built releases after it is merged: https://build.scilab.org/view/Scilab%206.0/
Samuel is right, unless you need an OSX version, for which the continuous build is discontinued.
mentioned in issue #15916 (closed)