-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting "line 33: `@out': not a valid identifier" #11
Comments
Now getting this:
I hope to understand the code in this It is the first time I saw the likes of
I infer that this is associating file descriptor 8 to the output of the function and redirecting it to null. I am not sure why exactly you used file descriptors 7 and 8. Do they refer to anything specific? |
After seeing for the first time the likes of
I am now well aware that you are opening file descriptors 7 and 8. And "bad file descriptor" seems to refer to usage of one which is not open. I am looking more at the code. Optimistically, I will eventually figure out what is going on. Of course, your response would also be much preferred. |
Sorry for my delayed replay, I've been quite busy recently. I'm not sure what the reason is. I've met a problem before where the bash executed in MinGW was WSL's. Can you send me more details? You can send me your wechat account id to my email (you can find it on my profile page) if you want ^_^ |
The pronunciation of the word "debug" is very simillar to Chinese pinyin "Di Ba Ge", so I choose the number "8" as the fd for debug output. Haha ;-P |
Can you respond to me via email? I just sent you bash code I wrote and use for searching files, which I hope to test more systematically with your bach. Thank you! |
I am also got the error on ArchLinux but it turned out that my script was calling sh rather than bash
So make sure you are actually running bash |
Perhaps '@Bach' should throw an error if executed in a non-bash shell? |
I am running Git Bash (version 4.4) in Windows.
source bach.sh
within the shell works fine, sometimes it givesHowever, when try to source this file within a
.sh
file, I getHow to resolve this? Thank you!
As an FYI,
uname
on my OS givesMINGW64_NT-10.0-22621
.Given that I would much interested in using this bash testing framework, I would also be willing to assist in the process of testing it on Windows (assuming it hasn't already been done to some extent). 也可以用中文跟我私下沟通。
The text was updated successfully, but these errors were encountered: