|in my starting scripts (which i prefer to the .pdrc-file) I get a very long |Wurst (as we say in austria - a very long line) of flags, because i think the |flags have to be in one line... is this true? and if i have more then one |path-flag, can i combine them in one command?
you can use a \ which tells the shell that the cmd is continued on the next line (wurstslicing operator ) like:
#!/bin/sh
pd
-lib Gem
-lib zexy
-etc etc
$@
with path dont know but just try
-path /path/eins:/path/zwei:/etc/usw
|also, there once was the problem of comments in the .pdrc file, is there
|already a solution, this also would make things easier?
|marius
|
|Am Donnerstag, 17. Januar 2002 12:06 schrieb Krzysztof Czaja:
|> hi Miller,
|>
|> this issue recurs quite often on pd-list. And, while you are changing
|> the way of .pdrc parsing, could you look at my .pdrc & pd-034'' post |> from Mon, 01 Oct 2001, and also my
.pdrc trouble (0.34-3 & 4)'' post
|> (and your reply to it) from Tue, 27 Nov 2001? Command line overriding
|> was mentioned there, and also some other points...
|>
|> Krzysztof
|>
|> Miller Puckette wrote:
|> > Looking at the source code, I gather that the ".pdrc" actually overrides
|> > command line! This is wrong... I'll fix for 0.35...
|
-- X Ð ¥ · 0 r G