I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
on both windows and linux (I don't use mac), you only have to give the
file name as an argument, no -open flags are necessary. It's also possible
to give several files as argument to open them all (on my .bat file I use
%1 %2 %3 %...)
Joao
Am 29.06.2006, 19:05 Uhr, schrieb chris clepper cgclepper@gmail.com:
I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
João Miguel Pais wrote:
on both windows and linux (I don't use mac), you only have to give the file name as an argument, no -open flags are necessary. It's also possible to give several files as argument to open them all (on my .bat file I use %1 %2 %3 %...)
when i start pd from the shell, i usually use "pd -lib bla patch.pd" when i start pd from a script, i usually use "pd -lib bla -open patch.pd"
in my experience it is sometimes necessary (or at least far less complicated) to use the "-open" flag instead of relying on the "everything after the last flag (or what i think is the last flag) is a pd-patch to be opened" (especially because is not really very good in detecting 'the last flag'.
mgh.adf IOhannes
On Fri, 30 Jun 2006, IOhannes m zmoelnig wrote:
when i start pd from the shell, i usually use "pd -lib bla patch.pd" when i start pd from a script, i usually use "pd -lib bla -open patch.pd"
Bash parses and runs a script exactly the same as something on the commandline (with the possible exceptions of "!" and "#" but that's not relevant here)
You must mean .pdrc, which is *not* run as a shell script. However, I have just tried without -open and it still works the same. The main difference between .pdrc and bash (both script and commandline) is that .pdrc lacks quoting, which makes it not possible to specify spaces in paths because what pd parses "foo bar" as, bash would get it from ""foo" "bar"".
_ _ __ ___ _____ ________ _____________ _____________________ ... | Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju | Freelance Digital Arts Engineer, Montréal QC Canada
Mathieu Bouchard wrote:
On Fri, 30 Jun 2006, IOhannes m zmoelnig wrote:
when i start pd from the shell, i usually use "pd -lib bla patch.pd" when i start pd from a script, i usually use "pd -lib bla -open patch.pd"
Bash parses and runs a script exactly the same as something on the commandline (with the possible exceptions of "!" and "#" but that's not relevant here)
You must mean .pdrc, which is *not* run as a shell script. However, I
no i don't mean .pdrc i mean "running pd from the shell" vs. "running pd from a shell script".
i do know that this is actually the same thing. still i do use "-open" in scripts while i don't use it when i run pd directly from the shell.
the latter usually applies to "simple" startups and then i am too lazy to use the "-open" flag.
i only write scripts when the startup gets complicated (well not entirely true: i also write scripts when the whole thing has to be started by a person who has no shell knowledge. or by an init-script). and as soon as it gets complicated, i found the "-open" option very useful. the most important thing for me is, that you can specify arguments _after_ you have told pd to load a patch.
mfg.asdr IOhannes
Yeah, I have that problem as well. Maybe we should file a bug? Can
anyone get -open to work on Mac OS X with Pd >=0.39?
.hc
On Jun 29, 2006, at 1:05 PM, chris clepper wrote:
I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
however i can open a patch by just providing the path to the file
without the -open
if this is what you mean.
m.
Am 05.07.2006 um 06:27 schrieb Hans-Christoph Steiner:
Yeah, I have that problem as well. Maybe we should file a bug?
Can anyone get -open to work on Mac OS X with Pd >=0.39?.hc
On Jun 29, 2006, at 1:05 PM, chris clepper wrote:
I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
i use a .command file where -open works fine with millers pd-0.39-2.app using the same .command file with pd-extended opens wishshell.app the main pd-window appears but not my patch.
On Jul 5, 2006, at 6:27 AM, Hans-Christoph Steiner wrote:
Yeah, I have that problem as well. Maybe we should file a bug? Can
anyone get -open to work on Mac OS X with Pd >=0.39?.hc
On Jun 29, 2006, at 1:05 PM, chris clepper wrote:
I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Computer science is no more related to the computer than astronomy is
related to the telescope. -Edsger Dykstra
PD-list@iem.at mailing list UNSUBSCRIBE and account-management ->
http://lists.puredata.info/listinfo/pd-list
Unfortunately, Miller's Mac OS X build system isn't publically
available, so I can't tell what he's doing differently...
.hc
On Jul 5, 2006, at 3:50 AM, Enrique Erne wrote:
i use a .command file where -open works fine with millers
pd-0.39-2.app using the same .command file with pd-extended opens wishshell.app the main pd-window appears but not my patch.On Jul 5, 2006, at 6:27 AM, Hans-Christoph Steiner wrote:
Yeah, I have that problem as well. Maybe we should file a bug?
Can anyone get -open to work on Mac OS X with Pd >=0.39?.hc
On Jun 29, 2006, at 1:05 PM, chris clepper wrote:
I would like to pass the -open argument to 0.39 so I can use a shell script to open Pd with specified patches. I can only get -open to work in the settings dialog.
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
Computer science is no more related to the computer than astronomy
is related to the telescope. -Edsger Dykstra
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/ listinfo/pd-list
On 7/4/06, Hans-Christoph Steiner hans@eds.org wrote:
Yeah, I have that problem as well. Maybe we should file a bug? Can anyone get -open to work on Mac OS X with Pd >=0.39?
.hc
I got the .app version to work with a flag by deleting everything in the preferences and using /Resources/bin/Pd rather than the executable in MacOS/
cgc
On Jul 5, 2006, at 11:32 AM, chris clepper wrote:
On 7/4/06, Hans-Christoph Steiner hans@eds.org wrote:
Yeah, I have that problem as well. Maybe we should file a bug? Can anyone get -open to work on Mac OS X with Pd >= 0.39?
.hc I got the .app version to work with a flag by deleting everything
in the preferences and using /Resources/bin/Pd rather than the
executable in MacOS/
So its a bug in Pd-extended, I am filing a a report in the tracker.
Anyone have any ideas what might be causing this?
.hc
-
chris clepper -
chris clepper -
Enrique Erne -
Hans-Christoph Steiner -
IOhannes m zmoelnig -
João Miguel Pais -
Mathieu Bouchard -
Max Neupert