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.

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

Allow interpreter hashbang on first line of document #440

Closed
guillaumekh opened this issue Feb 26, 2016 · 1 comment

Comments

@guillaumekh
Copy link

commented Feb 26, 2016

It is possible to write nodeJS scripts that are executable straight from shell.

To do so, one has to :

  • make the script executable (i.e. chmod +x)
  • add a "hashbang" at the beginning of the script to tell the shell which interpreter the script should be passed on to (e.g. #! /usr/local/bin/node)

Currently, standard issues the following warning for the hashbang :

Expected space or tab after "//" in comment.

The new behavior would throw no such warning.

Tested with linter-js-standard

@guillaumekh

This comment has been minimized.

Copy link
Author

commented Feb 26, 2016

I filled that issue too fast. It seems actually standard throws no warning. Sorry for the spam 😕

@lock lock bot locked as resolved and limited conversation to collaborators May 10, 2018

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
1 participant
You can’t perform that action at this time.