@IOhannes
> On 8/31/18 11:56 AM, rolfm(a)dds.nl wrote:
>> still, the searchpath-preferences are apparently different for
>> externals
>> and for plugins.
>
> i missed how the "plugins" (i assume you mean the extensions for the
> Pd-gui) entered the discussion here.
i don't know how to interprete this remark.
in the Pd-console i get this output:
loaded iem::punish::patcherize-plugin
loaded iem::punish::triggerize-plugin
'deken-plugin.tcl' already loaded, ignoring:
'D:/pd-0.48-1.msw/pd/extra/deken-plugin/deken-plugin.tcl'
patcherize - turn objects into a subpatch
triggerize - insert [trigger] ad lib.
for the plugins first the standard folder is inspected and after that
the (changed) path in my preferences.
there is no choice here for the user; besides removing (temporarely)
unwanted plugins from the standard folder.
>>
>> BTW is there a way to declare a .pdsettings in the command-line?
>> (i cannot find one).
>
> $ pd -help 2>&1 | grep -i pref
> -prefs -- load preferences on startup (true by default)
> -noprefs -- suppress loading preferences on startup
> -prefsfile <file> -- load preferences from a file
thanks for that.
trying this out i found:
the -prefsfile option does 'replace' the preferences.
the 'load from..' in the preferences menu adds the prefs from the file
to the existing ones.
it seems inconsistent, but one can also argue that this offers both
possibilities.
rolf
