<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix">Le 26/04/2021 à 14:51, Samuel Gougeon a
écrit :<br>
</div>
<blockquote type="cite"
cite="mid:aa3b4d46-d613-4643-ab38-084a1b47a0f9@free.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Le 26/04/2021 à 14:15, Stéphane
Mottelet a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:26a6b036-7a07-430d-be95-fab451a2257f@utc.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<blockquote type="cite"
cite="mid:b85299ec-de54-4477-dfa2-c76157623207@free.fr">.../...<br>
<p>Such a wish was reported 10 years ago as <a
moz-do-not-send="true"
href="https://antispam.utc.fr/proxy/1/c3RlcGhhbmUubW90dGVsZXRAdXRjLmZy/bugzilla.scilab.org/show_bug.cgi?id=6801">bug
6801</a>.<br>
<br>
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).<br>
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.</p>
For contribution,<br>
Samuel<br>
</blockquote>
<p>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 </p>
</blockquote>
</blockquote>
<p>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.<br>
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.<br>
</p>
<br>
</body>
</html>