At least that is what currently seems to be implemented. If no project specific configuration is given (i.e., just startup eeschema without any file) a kicad.pro template is searched in the search paths and the first one found would get copied to some default (preferences) location and used. As far as I have seen the method that should do copying just bails out because no destination is given. This leads to creating the very default “eeschema Preferences” (on OS X, don’t know about behaviour on Linux or Windows), which then always gets used/updated (as long as no project specific .pro file is there) instead of the default/template kicad.pro.
Regards, Bernhard > On 24 Feb 2015, at 18:01, LordBlick <lordbl...@gmail.com> wrote: > > In response to a message written on 24.02.2015, 16:51, from Wayne Stambaugh: >> The .pro file belongs in the path for each project. It should not >> contain system specific paths. It is created when you create a new >> project and contains the project specific settings. There is no way to >> save symbol library paths in the Eeschema application settings at this time. >> > I guess that template kicad.pro,on Unix based OS-es, copied from proper folder > to KiCAD configuration dir and modified with user preferences, would have > higher > priority in search patch, so every new project will have the same library set > without need of re-edit. > -- > Best Regards, > LordBlick > > _______________________________________________ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
