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

run on unsaved code? #35

Open
mspreij opened this issue Dec 23, 2015 · 1 comment
Open

run on unsaved code? #35

mspreij opened this issue Dec 23, 2015 · 1 comment

Comments

@mspreij
Copy link

mspreij commented Dec 23, 2015

I would like to run a syntax check on the source without saving (so if the syntax is broken, it'll keep working in the browser, where I might be testing other things at the same time).
Is this possible?

@rondevera
Copy link
Owner

Unfortunately not—JSLintMate is designed to only support saved files. Internally, JSLintMate passes file paths to JSLint and JSHint; it could potentially pass around a huge string of unsaved source code, but could get messy.

When I've been in this situation in the past, I've copied the unsaved source code into a new file, then saved and iterated on that. (You might already be doing this.) It's not the same, but it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants