actually it seems .pd is not mandatory, right?
Anyway I like this :)
pd -open "mypatch1.pd: 1 2 3" -open "mypatch2: foo bar"
Yes, the .pd extension is not mandatory! In fact, it doesn't even have to be a "real" Pd patch. You can also open a .txt file containing a list of arbitrary Pd messages.
On 09.06.2020 12:55, Mario Buoninfante wrote:
actually it seems .pd is not mandatory, right?
Anyway I like this :) pd -open "mypatch1.pd: 1 2 3" -open "mypatch2: foo bar"
Pd-list@lists.iem.at mailing list UNSUBSCRIBE and account-management -> https://lists.puredata.info/listinfo/pd-list
On 09.06.20 14:02, Christof Ressi wrote:
Yes, the .pd extension is not mandatory!
depends on what you mean with "mandatory".
what is mandatory is that the you specify a full filename (not necessarily the "full path"). if the filename ends with ".pd", you *must* also add the suffix when calling Pd. if the filename ends with ".flubber", you *must* also add the suffix when calling Pd. if the filename does not end with ".pd" you *must not* specify the (non-existing) extension.
you cannot leave out arbitrary parts of the filename.
and in general i would not advise to create Pd-patches without the .pd extension.
gdfasm IOhannes
-
Christof Ressi -
IOhannes m zmoelnig -
Mario Buoninfante