Re: [PD] [openpanel]/[savepanel] directory, [cd]
Quoting Rich E [EMAIL PROTECTED]:
Which brought me to another question; is there any way currently to do a
'cd' or 'pwd' in pd? I tried:
[pwd (
|
[shell]
but this has the same problem of openpanel and savepaned; it gives you the
path that pd was opened from.
seems to be what i would have expected...if [openpanel] thinks that
the pwd is X, why should $(pwd) think it differently.
[cd /home/full/path/to/patch (
|
[shell]
doesn't seem to do anything, and would be a workaround if it did.
it does and it has been discussed multiple times on this list:
sending a command to the [shell] will start a new process (shell), run
the command and quit. like it should be, child processes do not modify
parent processes and siblings.
you could as well do: start a new xterm; notice that you are in
${HOME}; run cd /tmp; close the xterm; start another xterm, notice
that you are still in ${HOME}
i am not sure what you would like to achieve with [pwd] or [cd]
that is: if you could manage with [pwd] and [cd], why can't you do so
with the current absolute/relative path in [openpanel]?
fmgads.
IOhannes
This message was sent using IMP, the Internet Messaging Program.
___
PD-list@iem.at mailing list
UNSUBSCRIBE and account-management -
http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On 29/05/2008, at 4.09, Rich E wrote: Which brought me to another question; is there any way currently to do a 'cd' or 'pwd' in pd? Since your already on the external path you could use [getdir] from ggee. I tried: [pwd ( | [shell] but this has the same problem of openpanel and savepaned; it gives you the path that pd was opened from. [cd /home/full/path/to/patch ( | [shell] doesn't seem to do anything, and would be a workaround if it did. When using a [shell] object you'd really wanna run a script. Since it's a new shell that's opened each time you query it. So when you do [cd /to/som/dir(/[shell] and then after wards to [pwd(/ [shell] then you'r no longer cd'ed to /to/some/dir but get the root dir. You can make a simple shell-script that both cd and pwd and then run that script. That is if you want to use a [shell] object. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. -rich ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On Wed, 2008-05-28 at 23:57 -0700, Rich E wrote: it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. i agree with you, that this new feature of [openpanel] and [savepanel] is kind of bogus the way it is implemented now. in so many cases you rather would want to set a path relative to the patch instead of relative to pd start location. i personally think, that [[open][save]panel]s within abstractions should behave accordingly: path should be relative to the file location (the path that is written in the window title, when you open the window). the same goes for the 'open' message to pd: i can't think of a good reason for the actual behaviour. relative to the patch would make much more sense, IMO. i stop saying this over and over again, as soon as someone comes up with a really good explanation for the current implementation(sorry for being so strongheaded). roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
i agree with roman, but as was mentioned before, the [getdir] external is good if you need to find the directory of the current patch. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On May 29, 2008, at 10:04 AM, Roman Haefeli wrote: On Wed, 2008-05-28 at 23:57 -0700, Rich E wrote: it does and it has been discussed multiple times on this list: sending a command to the [shell] will start a new process (shell), run the command and quit. like it should be, child processes do not modify parent processes and siblings. Ah. This makes sense. i am not sure what you would like to achieve with [pwd] or [cd] that is: if you could manage with [pwd] and [cd], why can't you do so with the current absolute/relative path in [openpanel]? I was just looking for a quick hack to get my patches working that try to open up a specific directory using [openpanel]. But I guess the real solution is making [openpanel]/[savepanel] relative to the patch it they live in. I don't really know how this would work for an [openpanel]/[savepanel] within an abstraction. i agree with you, that this new feature of [openpanel] and [savepanel] is kind of bogus the way it is implemented now. in so many cases you rather would want to set a path relative to the patch instead of relative to pd start location. i personally think, that [[open][save]panel]s within abstractions should behave accordingly: path should be relative to the file location (the path that is written in the window title, when you open the window). the same goes for the 'open' message to pd: i can't think of a good reason for the actual behaviour. relative to the patch would make much more sense, IMO. i stop saying this over and over again, as soon as someone comes up with a really good explanation for the current implementation(sorry for being so strongheaded). I also think the default should be relative to the patch. I am not quite sure now to handle abstractions, that's worth discussing more. I don't have time to work on it now, but if someone posts a bug in the tracker (or feature request, if you think that's better), I'll try my hand at it later. It's always useful to include a link to web archive to related discussions like this in the bug tracker. On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? .hc roman ___ Telefonate ohne weitere Kosten vom PC zum PC: http:// messenger.yahoo.de ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/ listinfo/pd-list http://at.or.at/hans/ ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? i would prefer it to be the directory where the original patch lives in. i hardly ever put any patches into my home directory (apart from ominous delme.pd's that keep popping up...:-)) fgmasdr IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? sounds good to me. ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
Re: [PD] [openpanel]/[savepanel] directory, [cd]
IOhannes m zmoelnig a écrit : Hans-Christoph Steiner wrote: On a related note, for this release, I made Save As default to the Home folder (~/), what do people think about that? i would prefer it to be the directory where the original patch lives in. i hardly ever put any patches into my home directory (apart from ominous delme.pd's that keep popping up...:-)) same here. vincent fgmasdr IOhannes ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
[PD] [openpanel]/[savepanel] directory, [cd]
Hi all, I noticed the nice, new feature in [openpanel] and [savepanel] to specify a directory to open in. This saves much, much time navigating to the right directory. But it seems to only work if you specify the full path or the directly lays in the relative path of where pd was opened from (which is almost never the case on Mac, and hardly ever on other systems). It should open from anything within the relative path of where the patch is. Which brought me to another question; is there any way currently to do a 'cd' or 'pwd' in pd? I tried: [pwd ( | [shell] but this has the same problem of openpanel and savepaned; it gives you the path that pd was opened from. [cd /home/full/path/to/patch ( | [shell] doesn't seem to do anything, and would be a workaround if it did. regards, Rich ___ PD-list@iem.at mailing list UNSUBSCRIBE and account-management - http://lists.puredata.info/listinfo/pd-list
