Hi,
I find that my Pd does do autopatching despite -noautopatch being specified in my ~/.pdrc which makes me wonder if that file is read at all? Or has the name/location of pd's config file changed by now? This is with Pd-0.47.1 ("") compiled for Debian (0.47.1-3) installed via Debian apt.
Thanks! P
On 04/13/2017 10:39 PM, Peter P. wrote:
Hi,
I find that my Pd does do autopatching despite -noautopatch being specified in my ~/.pdrc which makes me wonder if that file is read at all? Or has the name/location of pd's config file changed by now? This is with Pd-0.47.1 ("") compiled for Debian (0.47.1-3) installed via Debian apt.
Pd's config-file on linux is called ~/.pdsettings for about a decade (or longer). iirc, it will fallback to ~/.pdrc, but only if it cannot find a ~/.pdsettings.
oh, and btw: autopatching is *really* nice (mostly).
- zmoelnig@iem.at zmoelnig@iem.at [2017-04-13 18:36]:
On 04/13/2017 10:39 PM, Peter P. wrote:
Hi,
I find that my Pd does do autopatching despite -noautopatch being specified in my ~/.pdrc which makes me wonder if that file is read at all? Or has the name/location of pd's config file changed by now? This is with Pd-0.47.1 ("") compiled for Debian (0.47.1-3) installed via Debian apt.
Pd's config-file on linux is called ~/.pdsettings for about a decade (or longer).
Thank you! Feels good to have arrived in this decade.
iirc, it will fallback to ~/.pdrc, but only if it cannot find a ~/.pdsettings.
In my case ~/.pdsettings was empty, hence pd didn't fall back to .pdrc
Does pd write into .pdsettings itself by the way? What if I don't want that?
oh, and btw: autopatching is *really* nice (mostly).
Oh absolutely! There is nothing wrong with it. I simply want to spare me the extra click onto the canvas to de-select the currently created object before creating a new one.
Thanks again, P
Strangely neither setting
-noautopatch
nor
noautopatch
in my ~/.pdsettings disables autopatching. Specifying it on the command line does work though. Can anyone else reproduce this?
best, P
Hi,
With no ~/.pdsettings, putting -noautopatch into my ~/.pdrc works as expected. Tested with:
$ pd -version Pd-0.47.1 ("") compiled for Debian (0.47.1-3) on 2016/11/28 at 20:56:10 UTC
On 13/04/17 23:58, Peter P. wrote:
Strangely neither setting
-noautopatch
nor
noautopatch
in my ~/.pdsettings disables autopatching. Specifying it on the command line does work though. Can anyone else reproduce this?
~/.pdsettings has a strange format, more complex than ~/.pdrc - it's meant to be edited and saved via the GUI.
Claude
On 04/14/2017 12:58 AM, Peter P. wrote:
Strangely neither setting
-noautopatch
nor
noautopatch
in my ~/.pdsettings disables autopatching. Specifying it on the command line does work though. Can anyone else reproduce this?
sure thing. this is mainly because ~/.pdsettings works differently from .pdrc (which just had one-cmdline-arg per line). instead, .pdsettings uses key/value pairs with the "keys" being predefined and not corresponding to any cmdline args, so "autopatch: 0" is not a valid setting here (and "noautopatch" or "-noautopatch" are totally not). luckily you can specify cmdline-args in the "flags" section, so having "flags: -noautopatch" should do what you want.
fmards IOhannes
- zmoelnig@iem.at zmoelnig@iem.at [2017-04-14 08:48]:
[...]
this is mainly because ~/.pdsettings works differently from .pdrc (which just had one-cmdline-arg per line). instead, .pdsettings uses key/value pairs with the "keys" being predefined and not corresponding to any cmdline args, so "autopatch: 0" is not a valid setting here (and "noautopatch" or "-noautopatch" are totally not). luckily you can specify cmdline-args in the "flags" section, so having "flags: -noautopatch" should do what you want.
Thank you! This indeed works!
best, P
On 04/14/2017 12:56 AM, Peter P. wrote:
Does pd write into .pdsettings itself by the way?
yes.
What if I don't want that?
then you shouldn't click on "save" in any of the properties/settings dialogs.
oh, and btw: autopatching is *really* nice (mostly).
Oh absolutely! There is nothing wrong with it. I simply want to spare me the extra click onto the canvas to de-select the currently created object before creating a new one.
i find it faster to just switch from/to edit-mode with <Ctrl>+<e>-<Ctrl>+<e>. this will deselect the current object without a click.
gmadsr IOhannes
-
Claude Heiland-Allen -
IOhannes m zmölnig -
Peter P. -
zmoelnig＠iem.at