I tried mr out on Bash on Windows.
I found that mr does not work so well.
Steps to reproduce the problem:
15:12:57 Andrew@LAPTOP-V9S562AR:~
$ mr s
mr s: /home/Andrew/.config/vcsh/repo.d/author.git
mr s: received signal 127
The status action does not cover a number of my repos, it just stops at the first repo.
I have installed mr via sudo apt-get install mr.
It seems that, when it tries to run a command that is not available, or if waiting for the command somehow fails, mr incorrectly interprets the resulting -1 exit code as a signal 127. I suspect that is what happened here. I've fixed mr to say "failed to execute" and give the system error message in this case.
As to why this would happen in WSL, I don't know. Other than WSL not being a perfect linux system call emulation. Hopefully the above fix will let mr report what the actual problem is.
Thank you for the clear error reporting update of
mr. The hidden error turns out to bemr update: failed to execute: Bad file descriptorNow I believe that WSL is responsible for this as it have incomplete Unix filesystem compared to Unix. Can thisBad file descriptorbe triggered becausemrwas acting on bad file descriptor number?