just been reading a few docs on pd and a couple of times it has been mentioned to "put it in your .pdrc file". i'm kinda, sort of, new to linux but i assume its some sort of launching device. could someone please explain to me how i use it and perhaps an example. thanks tom
On Monday 09 February 2004 20:10, tdunstan@ihug.com.au wrote:
just been reading a few docs on pd and a couple of times it has been mentioned to "put it in your .pdrc file". i'm kinda, sort of, new to linux but i assume its some sort of launching device. could someone please explain to me how i use it and perhaps an example. thanks tom
Assuming you've come to Linux after using that Microsoft Winders, or WinDos, or whatever they call it, then a "dot file" in Linux is similar to the old Win 3.x .ini files. It's not a launching device, as you say, but just a list of initialization options.
Usually you will create these files called "." + what ever the name of the program is, in your home directory, to customize your startup of that program. For example, if you use the Emacs editor, you might have a ".emacs". Or sometimes "rc" is appended, for example in the case of pd, where it's called ".pdrc".
Anyhow, typically, but not always, these files are just lists of command line arguments, only that usually you can use the carriage return as a a seperator as well.
Here is my (bloated at the moment) ".pdrc": ~ ~ ~ -path ~/cur -path ~/pd -path ~/pd/util -path ~/pd/test -path ~/pd/ins -path ~/pd/help -path /usr/lib/pd/externs -path /usr/local/lib/pd/externs -path /usr/lib/pd/extra -path /usr/local/lib/pd/extra/vasp/pd -path ~/k_quile -lib ~/xeq/xeq -lib /usr/lib/pd/extra/iemlib1 -lib /usr/lib/pd/extra/iemlib2 -lib vasp/vasp ~ ~ ~
Larry Troxler
tdunstan@ihug.com.au wrote:
just been reading a few docs on pd and a couple of times it has been
mentioned
to "put it in your .pdrc file". i'm kinda, sort of, new to linux but
i assume
its some sort of launching device. could someone please explain to me
how i use
it and perhaps an example. thanks tom
Under linux files with names starting with '.' are 'invisible', in that they don't show up when you do 'ls'. If you do 'ls -a' then you will see them. Usually these files are used to store user preferences for various programs. The file '.bashrc' contains things that control how your shell behaves when you open a terminal window. '.pdrc' can contain things like the path that pd searches for libraries. From a search for 'pdrc' in files in my pd-0.37-0/src/, in the function int sys_rcfile(void) in the file s_path.c, it loads the file pdrc into a buffer and then calls the function int sys_argparse(int argc, char **argv) in the file s_main.c, which is the same function that parses a command line. So basically it just reads '.pdrc' as though it was a command line, but you can probably put the parameters on separate lines for legibility and ease of editing. You can type pd --help for a list of available parameters.
Martin
.pdrc is a simple text file that you put in your home directory (i.e. /home/me). the idea is that flags you would normally provide in the command line when starting pd, you put in this file and don't have to write them each time. for example, if every time you start pd you want to have it recognize the path /home/me/pdpatches and use the lib iemlib, you could start each time with "pd -path /home/me/pdpatches -lib iemlib", or you could just put everything afer the "pd" into a file .pdrc you create in your home directory which pd automatically recognizes. no if you want to include flags sometimes when starting pd, you can use these and it will recognize both these and the ones in the .pdrc file.
here's an example of my .pdrc file: -nomidi -path /home/arkadyan/pd/patches -lib maxlib -lib iemlib1 -lib iemlib2 -lib iem_t3_lib -lib iem_mp3 -lib zexy -lib cyclone -lib OSC -lib flite -lib ratts
i gathered all this by trying mostly, so please correct me anyone if i've got anything wrong.
matt
tdunstan@ihug.com.au wrote:
just been reading a few docs on pd and a couple of times it has been mentioned to "put it in your .pdrc file". i'm kinda, sort of, new to linux but i assume its some sort of launching device. could someone please explain to me how i use it and perhaps an example. thanks tom
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
.pdrc is a file you should put in your home directory (i.e.: ~/ or /home/[your username]/) and it can include any commandline switch you usually use to launch pd.
If you do the command 'ls -a' in your home dir, you will probably see many dot files listed.
mine looks like this:
-mididev 3 -path /usr/local/lib/pd/externs:/home/mis/pdWork/MiSlib:/home/mis/pdWork/abstrus:/home/mis/pdWork/jimmies:/usr/local/lib/pd/externs/abs:/usr/local/lib/pd/extra:/home/mis/downloads/pd:/home/mis/pdWork/py:/usr/local/lib/pd/externs/mp3cast~:/usr/local/lib/pd/externs/cyclone -helppath /home/mis/downloads/cyclone-help -lib /usr/local/lib/pd/extra/zexy -lib /home/mis/pdWork/gripd/gripd -lib /home/mis/pdWork/d_mp3/d_mp3
[... many other -lib entries ...]
HTH
tdunstan@ihug.com.au writes:
just been reading a few docs on pd and a couple of times it has been mentioned to "put it in your .pdrc file". i'm kinda, sort of, new to linux but i assume its some sort of launching device. could someone please explain to me how i use it and perhaps an example. thanks tom
PD-list mailing list PD-list@iem.at http://iem.at/cgi-bin/mailman/listinfo/pd-list
-
Larry Troxler -
Martin Peach -
matthew shanley -
Michal Seta -
tdunstan＠ihug.com.au