Oftentimes, a program that you are working on contains relative references to files, and will not work unless the ScreenShell program is launched in the same working directory as the script.
If you launch :ScreenShell when you are not in a screen session, the bootstrapped screen session's CWD is the same as that of vim's, happily coinciding.
If you are in a screen session, the new ScreenShell's CWD is that of the screen session, which is likely not the same as Vim's CWD. :(
Right now I have a mapping that clumsily sends ScreenShellSend('cd '.getcwd()), but it would be nice if Screen.vim could do this (better) on init.
Oftentimes, a program that you are working on contains relative references to files, and will not work unless the ScreenShell program is launched in the same working directory as the script.
If you launch :ScreenShell when you are not in a screen session, the bootstrapped screen session's CWD is the same as that of vim's, happily coinciding.
If you are in a screen session, the new ScreenShell's CWD is that of the screen session, which is likely not the same as Vim's CWD. :(
Right now I have a mapping that clumsily sends
ScreenShellSend('cd '.getcwd())
, but it would be nice if Screen.vim could do this (better) on init.