Can some one tell me why windows Emacs still does not have a working shell?
One cannot easily run ssh from a shell in windows emacs. I have found that I cannot push to a bitbucket repo that uses http authentication too from the shell. But if I run them from a cmd window, these works fine.
What is the technical issue that is preventing emacs from fixing this?
As far as I understand this, this is a problem with git on Windows. Shells work just fine with Emacs on Windows, it just can't supply the git password for some reason.
Except they don't. File-name completion replaced all backslashes with forward slashes, thus breaking cmd.exe's built-in commands. I reported a bug; it started a short discussion; i was asked whether I had to use cmd.exe (YES, I have reasons for why I MUST use it); nobody really acknowledged it was a bug; the discussion died off in talk about some internal details. (The 24.4 binary package is not yet available for windows so I couldn't test it.)
I actually had a similar problem in the past. My workaround was to use some utilities from gnuwin32, which are native windows ports of the gnu utilities. With that, you can use gnu mkdir, rm, ls etc instead of the cmd builtins.
That is me! That is why I said 'One cannot easily run ssh..'. There are work arounds, like using plink or cygwin emacs and more. But it seems that every one of them is broken in some aspect. For eg, If I use cygwin, the cygwin file paths send to other command line programs (non cygwin) wont work with them. When using plink, the display of escape sequences in the command prompt, like "^[]0;vagrant@ubuntu-14:", and difficulty in working with programs like vagrant that uses ssh indirectly.
And as far as I saw, none of them provides a working auto completion in the context of remote file system. Another thing is that I cannot push to a remote repo using http authentication.
One cannot easily run ssh from a shell in windows emacs. I have found that I cannot push to a bitbucket repo that uses http authentication too from the shell. But if I run them from a cmd window, these works fine.
What is the technical issue that is preventing emacs from fixing this?