[Scilab-users] Toolboxes startup
Samuel Gougeon
sgougeon at free.fr
Mon Apr 26 12:38:51 CEST 2021
Hello,
Le 26/04/2021 à 09:41, Stéphane Mottelet a écrit :
>
> Hi all,
>
> I just made available for macOS and Linux the toolboxes stixbox
> depends upon for macOS (distfun and linalg) and my remark is that when
> a lot of modules are loaded at startup then the output can become very
> long and sometimes messy, since we don't impose a normalized output:
>
> *Scilab branch-6.1 (Apr 19 2021, 23:19:29)**
> *
>
> *Start Distfun**
> **
> **Start Helptbx**
> **
> **Start Specfun**
> **
> **Start Makematrix**
> **
> **Start Apifun**
> ** Load macros**
> ** Type "help apifun_overview" for a quick start.**
> **
> **Start Linalg**
> **
> **Start Stixbox*
>
> I would rather expect something like:
>
>
> *Scilab branch-6.1 (Apr 19 2021, 23:19:29)**
> *
>
> *Start modules: Distfun, Helptbx, Specfun, Makematrix, Apifun, Linalg,
> Stixbox.*
>
> *--> *
>
> The verbosity level of the output (with the above default) could be
> defined in user preferences, and checked in module startup script in
> order to output the required amount of information.
>
> That's just a propostion to be discussed, of course.
>
Such a wish was reported 10 years ago as bug 6801
<http://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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.scilab.org/pipermail/users/attachments/20210426/2ddca5e7/attachment.htm>
More information about the users
mailing list