Skip to content
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.

Sign up for GitHub

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

Jump to bottom

bad interpreter: /bin/sh^M: no such file or directory #15

Open
mikecarr opened this issue Dec 5, 2023 · 2 comments
Open

bad interpreter: /bin/sh^M: no such file or directory #15

mikecarr opened this issue Dec 5, 2023 · 2 comments

Comments

@mikecarr
Copy link

mikecarr commented Dec 5, 2023

I just installed this, using brew, on my WSL Debian bookworm insance and when I ran the command I got this error:

zsh: /home/linuxbrew/.linuxbrew/bin/kns: bad interpreter: /bin/sh^M: no such file or directory
@mikecarr
Copy link
Author

mikecarr commented Dec 5, 2023

I just ran dos2unix on the file dos2unix /home/linuxbrew/.linuxbrew/Cellar/kns/7e5f78b781c6567f71068585f2b101caca99f0ef/bin/kns and it is working now

@cmeury
Copy link
Contributor

cmeury commented Oct 7, 2024

I just checked the two files in the repo, both don't have any unexpected characters. The shebang line ends with 0x0A (LF), the newline control character on both Linux and MacOS. Nothing unexpected, not sure what's happening here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@cmeury @mikecarr