-
Notifications
You must be signed in to change notification settings - Fork 0
Also see Known Issues
If a command goes wrong, you can hit $ to access the git process buffer. There, the entire trace for the latest operation is available.
This key binding is only available inside Magit buffers. If you have invoked a Magit command from elsewhere you can use M-x magit-display-process RET
That is because point is not "window local". When one switches to a buffer then point from the window that was the last one to display the buffer in question, is used. If there were ever multiple windows displaying that buffer, the value of point can be surprising. This behaviour isn't unique to Magit. A lengthy explanation can be found here, it also mentions some packages that can be used to work around this issue.
For at least some people pushing to a remote repository using https fails because Git never writes the password prompt to stdout and Magit therefore cannot forward it to the user. This problem is not unique to Magit and it is unknown how to fix it.
The optimal workaround is to just never push using https. If you only ever push to Github you should adjust your configuration to use ssh instead, following these instructions. If you are forced to use https sometimes, then you can tell Git to use a graphical popup to read the password. Unfortunately that means that all passwords are read like this, so you might want to only evaluate the following before pushing with https. If you have to do so often add this to your init file instead.
(setenv "GIT_ASKPASS" "git-gui--askpass")You might also want to try Password caching and Using SSH over the HTTPS port. Please let as know if one of these options works for you, so that we can update this point.