Ok, my CVS server is down (harddrive), but I'm pretty sure this version is close to the latest (my one fear is that this isn't a complete fix of the dreaded menu bug - at least it didn't show up in my testing). I did a quick patch of the path name bug by simply subtituting the windows short name for the interpreter executable and the source file path. The down move crash in the environment settings didn't show up, so I'm pretty sure I fixed it, but possibly not. The code is also very messy and needs a clean up.
If anyone wants to see specific features added let me know. I'm thinking about adding user specified flags to actions for things like input/output redirection and specifying unix style vs windows style path names (the latter is important for pdb, the python debugger, for some reason it expects unix style "/" for pathname separators even on windows). debugger support within CB is a little trickier. I have it working for pdb in my python plugin (albeit with a patch to the C::B sdk), but making that sufficiently generic to handle any debugger that has redirectible output without requiring custom c/c++ code will take some work.
Two other things:
1. Thomas's alternative to wxExecute would probably come in handy here
2. Someone (probably me) should write the tutorial wiki entry for this plugin
[attachment deleted by admin]