[Scilab-users] Toolboxes startup

[Samuel Gougeon]

Le 26/04/2021 à 14:51, Samuel Gougeon a écrit :
> Le 26/04/2021 à 14:15, Stéphane Mottelet a écrit :
>>> .../...
>>>
>>> Such a wish was reported 10 years ago as bug 6801 
>>> <https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=6801>.
>>>
>>> To me, the only way to overcome any mprintf or disp made in *.start 
>>> files of external modules would be to become able to redirect the 
>>> standard output to null (or anywhere else as in a file, as with 
>>> diary, that forks the stream instead of redirecting it).
>>> I don't think that %toolboxes aims to become public. 
>>> atomsGetInstalled() and atomsGetLoaded() (and others) would likely 
>>> be more suited to test the atoms status.
>>>
>>> For contribution,
>>> Samuel
>>
>> Yeah that's the idea. But better than redirection of the standard 
>> output, all the stuff displayed in the .start file should go in a 
>> Journal, to which display methods can be associated. So instead of 
>> explicitely calling disp or mprinf, etc. the .start script should 
>> just add some stuff + associated verbosity level to the journal. What 
>> would be actually really displayed
>>
Whatever is the method -- redirection of stdout to a file or special 
diary  --, i am afraid that the analysis of contents vs verbosity would 
then be done only after completing the whole loading process.
This would prevent displaying information in a progressive way : 
immediately after loading macros, then after loading the documentation, 
etc... that will anyway be required in some occasion.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20210426/3f5d1603/attachment.htm>