[PD-dev] path external(s)

B. Bogart ben at ekran.org
Wed Nov 17 20:48:08 CET 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I think your naming scheme makes a lot of sense Frank,

Is this stuff then soon going into CVS?

B.

Frank Barknecht wrote:
| Hallo,
| guenter geiger hat gesagt: // guenter geiger wrote:
|
|
|>I have hacked up obj1.c in order to provide the functionality, file is
|>attached, use the makefile from doc/6.externs to compile it.
|>
|>It does not give the path of the parent patch but of the main patch,
|>but this can easily be changed in the new routine.
|
|
| I finally tested this, made a help patch, edited the makefile and all
| is well. It's working great, I only wonder, if the name "pwd" is good.
| Is the topmost patch indeed the working directory? Also an external
| for getting at the children's working directories could be useful.
| Maybe [pwd] or [pwdir] should just print the directory containing a
| patch, [parentdir] could print the directory of the direct parent, and
| [topdir] would print the main patch's dir?
|
| Anyway, attached is the original package.
|
| Ciao
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFBm6r4jbOsMZSA25cRAl3EAJwNzGLu65+6CfF6YMXjitFK106giwCgnCfI
0tiWNo93aGnpnMRqfCi1BeA=
=0tmI
-----END PGP SIGNATURE-----




More information about the Pd-dev mailing list