Just noticed this one recently. (Never really had any need to use pushd or popd outside of a batch script, which would've been executed by cmd.exe if run in PyCmd) Is there any reason this couldn't just be implemented as an internal command, maintaining a stack of folders with a list (Like the DirectoryHistory class does now), and just facilitating a call to the existing internal implementation of chdir?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Implementing the simple case is trivial, of course. But due to the fact that PyCmd doesn't really parse or execute commands but dispatches them to cmd.exe (same old problem...), handling e.g. compound commands like "make && (if exist hello.exe popd) && make clean" is virtually impossible. And since "partial" support is usually confusing, I thought it's best to call this "unsupported".
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just noticed this one recently. (Never really had any need to use pushd or popd outside of a batch script, which would've been executed by cmd.exe if run in PyCmd) Is there any reason this couldn't just be implemented as an internal command, maintaining a stack of folders with a list (Like the DirectoryHistory class does now), and just facilitating a call to the existing internal implementation of chdir?
Implementing the simple case is trivial, of course. But due to the fact that PyCmd doesn't really parse or execute commands but dispatches them to cmd.exe (same old problem...), handling e.g. compound commands like "make && (if exist hello.exe popd) && make clean" is virtually impossible. And since "partial" support is usually confusing, I thought it's best to call this "unsupported".