search

cwjohan / markdown-to-html

Command-line utility to convert Github Flavored Markdown to HTML.
MIT License
236 stars 86 forks source link

env: node\r: No such file or directory #11

Open dcsan opened 7 years ago

dcsan commented 7 years ago

i'm getting the error below, using a global install...

$ markdown taxi.md
env: node\r: No such file or directory
nronnei commented 7 years ago

Having the same problem. Just used this package for the first time today. On Ubuntu 16.04 using Node 6.5 via NVM.

Entering markdown notes.md produces this error: /usr/bin/env: ‘node\r’: No such file or directory

Is this because I'm using nvm?

dcsan commented 7 years ago

I'm using TJ's n so its not that. I was on 6.4 i think.

cwjohan commented 7 years ago

Oh, I see it's complaining it cant find "node" with a carriage return immediately after it. That's an end of line encoding error for Unix/Linux but works OK in Windows. I attempted to strip those out. Somehow they got put back in. You can run fromdos or dos2unix to strip the carriage returns out of any script file.

On Sat, Oct 22, 2016 at 2:44 PM, Nick Ronnei notifications@github.com wrote:

Having the same problem. Just used this package for the first time today. On Ubuntu 16.04 using Node 6.5 via NVM.

Entering markdown notes.md produces this error: /usr/bin/env: ‘node\r’: No such file or directory

Is this because I'm using nvm?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cwjohan/markdown-to-html/issues/11#issuecomment-255555807, or mute the thread https://github.com/notifications/unsubscribe-auth/AH5q3DqdLrlcuR0BwXW6yybcw0eZGibCks5q2oO4gaJpZM4Kd1ev .

cwjohan commented 7 years ago

dc,

I have no idea how that error could occur. There is no "taxi" anything in markdown-to-html. No file name and not in the source code, as far as I know. Certainly not in the code I wrote myself.

Cheers, Craig

On Sat, Oct 22, 2016 at 4:32 AM, dc notifications@github.com wrote:

i'm getting the error below, using a global install...

[~/dev/rikai/chinese-study/docs]$ markdown taxi.md env: node\r: No such file or directory

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cwjohan/markdown-to-html/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/AH5q3LOuMxQiW4bz_fCrwf4u3sYILf0nks5q2fRSgaJpZM4Kd1ev .

cwjohan commented 7 years ago

We may need to restrict the dependencies to older or original versions rather than the latest, since I can see one test failing when all dependencies are the latest ones.

On Sat, Oct 22, 2016 at 10:34 AM, Craig Johannsen cwjohan@gmail.com wrote:

dc,

I have no idea how that error could occur. There is no "taxi" anything in markdown-to-html. No file name and not in the source code, as far as I know. Certainly not in the code I wrote myself.

Cheers, Craig

On Sat, Oct 22, 2016 at 4:32 AM, dc notifications@github.com wrote:

i'm getting the error below, using a global install...

[~/dev/rikai/chinese-study/docs]$ markdown taxi.md env: node\r: No such file or directory

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/cwjohan/markdown-to-html/issues/11, or mute the thread https://github.com/notifications/unsubscribe-auth/AH5q3LOuMxQiW4bz_fCrwf4u3sYILf0nks5q2fRSgaJpZM4Kd1ev .

bartonhammond commented 7 years ago

Same thing on my Mac

 markdown
env: node\r: No such file or directory
nronnei commented 7 years ago

@cwjohan I don't think @dcsan was saying you did write anything called taxi.md unless there is a deleted comment somewhere that I'm not seeing. Sounds like you've isolated the problem. Thanks for that and thanks for getting back to us! I must admit, however, that I found another software solution.

Not sure what your workflow looks like, but this Grunt plugin could prevent this issue in the future.

cwjohan commented 7 years ago

Thanks, Nick, for pointing to grunt-lineending. I used to use grunt a fair amount. Now, not so much.

Here's some advice that may help those with line ending issues. https://help.github.com/articles/dealing-with-line-endings/

I have recently had core.autocrlf set to only output lf. I don't ever want to see crlf myself. I'm using the git bash environment on Windows 10 and it is happy with the unix choice for line endings. However, I might have to refresh my repository to ensure that everything now is in the desired format.

I've run dos2unix on the scripts in the bin directory and re-published them with the tag v0.0.13, which also is the latest version. Hopefully, this finally will fix the line endings in the bin directory. ​Let me know if there still is a problem with that.

I had to add a comment line to each file because a change to the line endings only was white space and git didn't consider that sufficient for "git add" to do anything with the file.

dcsan commented 7 years ago

hi - I just included my instructions which was to use $ markdown $FILENAME resulting in the error.

So it seems the problem is you're developing on windows, and somehow something slipped through that wasn't *nix compatible. Usually its the other way around with windows users complaining, so this is a first!

nronnei commented 7 years ago

Wow, great article from the help section, thanks!