Re: -path vs. -open (follow-up)

I now find that after all flag options are dealt with, what's left is presumed to be the .pd file to open, so that just typing "pd adsr.pd" opens the patch as one would expect. So that so long as "open" is clearly documented as an alias for "lib" (if that is what it is retained as ), I have no problems - I can set up Windows command strings accordingly. It might be as well to document this behaviour as "pd [flags] file.pd", in the usage message.

Richard Dobson

I wrote:

anyway, there is an issue under Windows which I have been fiddling with

• file-association based launching, i.e. double-clicking a pd file to

launch it in PD. the default Windows mechanism is to send a program the command "open" as a command-line argument, together with the selected filename.