It is .Scilab, not .scilab (I know we should switch to full lower case). It is not part of our priority as you can see with the date of our bug report here: http://bugzilla.scilab.org/show_bug.cgi?id=3386
Especially since it won't break some works without bringing much... S On 21/09/2012 15:28, Guillaume Horel wrote: > Well unfortunately I don't and it's causing a bug... I'm trying to > understand why it was not created. I assume there is a piece of code that > creates it at startup if the directory doesn't exist right? Can anybody > reproduce the crash at startup it if they delete their .scilab directory? > > Thanks, > Guillaume > > On Fri, Sep 21, 2012 at 9:21 AM, Calixte Denizet < > [email protected]> wrote: > >> Hi Guillaume, >> >> Normally you should have a directory ~/.Scilab. >> >> Regards >> >> C >> >> >> On 21/09/2012 15:19, Guillaume Horel wrote: >> >> Thanks for the tip. Actually, I didn't have a SCIHOME directory (~/.scilab >> didn't exist). If I launch scilab with >> SCIHOME="~/.scilab" scilab >> it starts fine, and it saves some configuration files in there. However >> even for subsequent invocations, I need to set SCIHOME in the environment, >> otherwise scilab doesn't launch, so looks like the SCIHOME variable is >> never initialized. I'll check if there was anything in SCIHOME when scilab >> didn't crash before commit a715ab13a22. >> >> Guillaume >> >> On Fri, Sep 21, 2012 at 3:04 AM, Vincent COUVERT < >> [email protected]> wrote: >> >>> Hi, >>> >>> Just remove your SCIHOME directory and Scilab will start. >>> >>> Regards, >>> Vincent >>> Le 21/09/12 02:43, Guillaume Horel a écrit : >>> >>> Hello, >>> >>> in preparation for the 5.4 release, I've been compiling trunk pretty >>> regularly on gentoo. Everything was working fine until recently. However >>> scilab doesn't even start now. It compiles and install fine, but bombs at >>> startup. If I launch it from the command line, I just see the following >>> exception printed: >>> java.lang.reflect.InvocationTargetException >>> >>> I've tracked it down to this commit (first commit when it started to >>> break): >>> >>> commit a715ab13a22b5e53d6d4f811ea44a24770ba7097 >>> Author: Calixte DENIZET <[email protected]> >>> Date: Wed Sep 5 11:40:59 2012 +0200 >>> >>> Bug 11838 fixed: Maximized state of a window was not saved in quitting >>> >>> The commit seems innocuous enough, but it completely breaks scilab for >>> me. Any idea what might cause this? >>> >>> Thanks, >>> Guillaume >>> >>> >>> >>> _______________________________________________ >>> dev mailing >>> [email protected]http://lists.scilab.org/mailman/listinfo/dev >>> >>> >>> >>> _______________________________________________ >>> dev mailing list >>> [email protected] >>> http://lists.scilab.org/mailman/listinfo/dev >>> >>> >> >> >> _______________________________________________ >> dev mailing >> [email protected]http://lists.scilab.org/mailman/listinfo/dev >> >> >> >> -- >> Calixte Denizet >> Software Development Engineer >> ----------------------------------------------------------- >> Scilab Enterprises >> 143bis rue Yves Le Coz - 78000 Versailles, >> Francehttp://www.scilab-enterprises.com >> >> >> _______________________________________________ >> dev mailing list >> [email protected] >> http://lists.scilab.org/mailman/listinfo/dev >> >> > > > > _______________________________________________ > dev mailing list > [email protected] > http://lists.scilab.org/mailman/listinfo/dev -- ----------------------------- Sylvestre Ledru Operations manager Community manager ----------------------------- Scilab Enterprises http://www.scilab-enterprises.com/ http://www.scilab.org/ ----------------------------- _______________________________________________ dev mailing list [email protected] http://lists.scilab.org/mailman/listinfo/dev
