Linting your code
jsl on the frontmost file and present the results all pretty‐like in an HTML window.
Clicking on a line number will bring your document back to the surface and move the cursor to that line so you can correct the error.
= instead of
== inside a conditional, or if you have a fallthrough in your
switch statement. Because each of these nitpicks can be incredibly helpful or incredibly annoying depending on the individual,
jsl lets the user switch them on or off individually. You can use the “Edit Lint settings” bundle command to decide what you want to get bugged about.
There’s one other Lint command in the bundle: “Quick Lint.” It eschews the HTML-formatted output, instead displaying the results of your Lint in a tooltip:
jsl deems your code lint‐free, it won’t show a tooltip, so you won’t even notice it unless your code gets fuzzy — at which point you can launch the full‐fledged lint and figure out what’s up. I find this command useful because I’d never remember to lint my code otherwise.
Compressing your code
Download the bundle
Behold! As always, I invite questions, comments, torches, and/or pitchforks.