On Tuesday 12 September 2017 09:03 PM, Jeff King wrote:
If I understand right, you typed "sivaraam" once, then the network
lagged, then you typed "sivaraam" again.
Almost there but I should have been more clearer. What I actually did was I
run `git push` and knowing it would ask for a username I started typing
it immediately
without looking at the terminal to notice that the request for the
username hasn't
shown up yet due to the slow network. the terminal was like this before
the request showed up,
$ git push
sivaraam
After the request showed up the terminal was like,
$ git push
sivaraamUsername for 'https://github.com' :
I thought the buffered input wasn't recognised as it didn't show up
after the request.
So, I typed the username once more to get this,
$ git push -u fork
sivaraamUsername for 'https://github.com' : sivaraam
Password for 'https://sivaraamsivaraam@xxxxxxxxxx :
I have been accustomed with this now a days that I don't do the same
mistake now. I thought
it would nice if this could be fixed as I have seen utilities show the
buffered input after the
request but as I stated before I'm not able to recollect which utility
it was (hope I had better
memory)
That isn't really something that Git can fix reliably. Reading those
characters and echoing them back to the terminal is handled by your
terminal driver (and potentially other things like ssh). Git may have
received "sivaraamsivaraam" all at once, depending on where the lag is.
I expected this but wasn't sure which "potential thing" was handling the
'https' handling in the background.
I guess it's 'curl' but not sure.
---
Kaartic
