Results 17 comments of Ron DeVera

Since reading and writing branch properties are two of the core functions of Twig, this usage most likely won't change. For each issue here: - Falling back to a Git...

This currently isn't supported for a couple of reasons: - An HTML document could have multiple `` blocks. - It can be tricky to correctly find `` blocks in a...

I haven't done anything here—feel free to take it on!

Hey Jérémy and Paul, Sorry I haven't commented on this sooner! I've been able to reproduce this locally, and keep circling back to it in hopes of fixing it. (I...

Some research in issue #9 considered using `iconv` to convert the JS file from UTF-8 to ISO8859-1 (which JSC can supposedly handle), but it didn't fail gracefully enough on some...

Interesting work, @noniq -- thanks for investigating! One of the project goals is to work out of the box, so node.js won't become a dependency. However, I'd be open to...

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,...

Hi Arne, Definitely. The setup steps are documented in the readme: 1. Set up `.tm_properties`: https://github.com/rondevera/jslintmate/#textmate-2 (just the "Project setup" part) 2. Set up an options file (separate from `.tm_properties`):...

Aha, thanks for clarifying; I like your idea. It looks like environment variables stored in `.tm_properties` are overridden by those in the "Linters" and "Options Files" settings. However, try this:...

@MokoJumbie It's definitely a nice convention from node-jshint, and it's been on my todo list to support it. The catch is that it would cause a lot of confusion/complications with...