Hans-Christoph Steiner wrote:
On Jun 10, 2010, at 3:09 PM, Kim Cascone wrote:
IOhannes m zmölnig wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 06/10/2010 06:59 PM, Kim Cascone wrote:
is there a way on the command line to load only certain libs?
this way I don't have to delete them and retype them in on the
'libraries to load on startup' panel
or is the simplest way to delete them from this list and put them back
in one by one?
the "paths" panel is mainly merely a graphical wrapper around the
"-path" flag.
e.g. "-path /path/to/lib1:/path2/lib2:/bla/blu"
true but doing this from a terminal will only add paths on a per
session basis
unless you open the 'paths' panel and click on Apply
is there a way to make this persistent from the console?
the "startup" panel is mainly merely a graphical wrapper around the
"-lib" flag.
e.g. "-lib Gem:zexy:iemguts"
ok thanks - will try adding one at a time and seeing which one causes
the [plugin~] crash
more later
The one that causes plugin~ to crash is likely 'flatspace' since it
includes the old, buggy version of plugin~.
yeah I already compiled the new [plugin~] and replaced the old one in
the /flatspace lib
so there is something else either in /flatspace or another lib causing
[plugin~] to crash when getting a [info] or [listplugins] message
but I'll isolate the new [plugin~] from the rest of the /flatspace and
see if that is true
If you put the plugin~.pd_linux into your project folder, it will be
loaded first.
by 'project folder' do you mean the '~/pd-externals' directory?
_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
