remote debug source mapping

the ability to specify a working directory in the remote launch configuration has been wired up. this is useful in situations where the remote source code needs to reside under a directory structure that differs from your local workspace. once again with the good news, bad news - breakpoints appear in the ruler context, but the debugger ignores them. when the dbgp 'set_breakpoint' command is sent, the location of the source in the local workspace is being used, instead of sending the path on the remote end. i also checked out why the breakpoints don't appear in the editor rulers of source that is looked up, and it appears i was correct - although it turns out that is an issue for any ISourceModule implementation using the ExternalStoragEditorInput (ie: interpreter libraries). oh well, labor day weekend is upon us and i'll be spending it at moe.down - hopefully i will return with a fresh perspective and sagely advice in my inbox from the dltk folks on how to proceed.