# Facing issues while using binstubs

**URL:** <https://meta.discourse.org/t/facing-issues-while-using-binstubs/190017>\
**Category:** Development\
**Created:** [May 11, 2021, 9:21am UTC](https://meta.discourse.org/t/facing-issues-while-using-binstubs/190017 "2021-05-11T09:21:07Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fzngagan](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/fzngagan/32/259349_2.png) [@fzngagan](https://meta.discourse.org/u/fzngagan)\
**Post date:** [May 11, 2021, 9:21am UTC](https://meta.discourse.org/t/facing-issues-while-using-binstubs/190017/1 "2021-05-11T09:21:08Z")

</div>

Recently, I’ve been getting errors while using binstubs on MacOS. My workflow is completely dependent on them.

```plaintext
env: ruby\r: No such file or directory

```

Looks like there’s some problem with line endings?

My temporary workaround is to use `ruby bin/unicorn` etc. While doing that, I get this warning `ruby: warning: shebang line ending with \r may cause problems`

Any pointers whould be super helpful. Any ideas @david

---

<div class="post-metadata">

**Author:** ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)\
**Post date:** [May 11, 2021, 10:22am UTC](https://meta.discourse.org/t/facing-issues-while-using-binstubs/190017/2 "2021-05-11T10:22:18Z")

</div>

Sounds like you have somehow ended up with windows-style line endings in the binstubs. Maybe you opened the files in Windows? Or switched your text editor to use windows-style line breaks?

What do you see if you run `file bin/unicorn`. I see this:

```plaintext
❯ file bin/unicorn
bin/unicorn: Ruby script text executable, ASCII text

```

If I manually change the line endings to Windows, I see the same error as you, and `file` shows me:

```plaintext
❯ file bin/unicorn
bin/unicorn: Ruby script text, ASCII text, with CRLF line terminators

```

^^ When things are in this broken state, it shows as a diff in Git, and running `git reset --hard` fixes things up.
