Closed BigRoy closed 9 years ago
I'm getting this too, not sure why, but thanks for flagging it, thought it might have been something local.
It did work at first, it seems to happen randomly. Smells like a MSYS2 bug.
Also with git bash (is that msys 1?) it seems to work great.
Yeah, that's MSYS1, good to hear that it works here. MSYS2 is newer and possibly not as complete yet.
Also, is it the intended behaviour that when not using --enter a non-existing folder is ignored thus won't be created?
Yes, this is intended. The idea is to not modify the file-system, but only the environment. Inside an environment, you can run . home
which will take you to your home directory, if it exists. In cmd.exe
, it's just home
. The .
means "source" which is a bash-thing.
It was an issue with not flushing stdout
after having written to it. This was the only instance where that was used, as it's the only occurrence of waiting for user input.
Should be fixed now.
When I
--enter
a non-existing folder with MSYS2 the message whether to create the folder doesn't show until after I entered my choice. The expected behaviour would be to see the question/message so I know what I'm responding to.Tested on Windows 7 64-bit .
MSYS2
After
--enter
the cursor will blink waiting for a response but doesn't show theCreate? [Y/n]
question. I can typen
and it will work fine, but since the question doesn't show until after you've entered a response you're basically in the dark of what you're responding to.The behavior is the same after
be activate
.cmd.exe & git bash (msys?)
Under cmd.exe it works fine and shows the question directly.
Also with git bash (is that msys 1?) it seems to work great.
Also, is it the intended behaviour that when not using
--enter
a non-existing folder is ignored thus won't be created?