It's really the same issue when you get down to it. IMO the command line flags should *not* save to the settings, but override what's in the settings at start. That matches command line flag behavior in pretty much all command line programs I've ever used and I see Pd saving those flag settings automatically an anomaly.
As stated in the PR, I vote we change that behavior and perhaps add a new flag like "-save" to allow saving the settings *with* the command line flags.
On Nov 11, 2017, at 12:00 PM, pd-list-request@lists.iem.at wrote:
there's a related PR on github (it doesn't solve your problem, but also tries to avoid spilling some cmdline options into the Pd-settings) https://github.com/pure-data/pure-data/pull/153 https://github.com/pure-data/pure-data/pull/153
Dan Wilcox @danomatika http://twitter.com/danomatika danomatika.com http://danomatika.com/ robotcowboy.com http://robotcowboy.com/
- Dan Wilcox danomatika@gmail.com [2017-11-12 19:39]:
It's really the same issue when you get down to it. IMO the command line flags should *not* save to the settings, but override what's in the settings at start. That matches command line flag behavior in pretty much all command line programs I've ever used and I see Pd saving those flag settings automatically an anomaly.
Thank you for your point of view!
As stated in the PR, I vote we change that behavior and perhaps add a new flag like "-save" to allow saving the settings *with* the command line flags.
Or just use the "Save all preferences" function in the "File" menu, since we should avoid introducing even more command line flags.
-
Dan Wilcox -
Peter P.