Update javascript.vim

[bounceme]

yesterday's commit was still a little buggy, sorry. this should be better

[amadeus]

Hope I'm not a pain, but can you outline what this fixes?

[bounceme]

mostly I think my usage of the search pair command was wrong, best to give an example though:

var magicWords = ['abracadabra', 'gesundheit', 'ventrilo'],
  spells = {
    'fireball': function() {
      setOnFire()
    },
    'water': function() {
      putOut()
    }
  },
  a = 1,
  b = 'abc',
  etc, somethingElse
someFunc(param1, param2,
  param3, param4)

at the moment this 'inMultiVarIndent' function traverses the curly braces of the spells object. I was close yesterday but for search pair you are generally going to have a few bugs. this is what the indent will look now, you can try with yesterday's and see the difference, basically the rest of the file is broken.

[bounceme]

by the way, @amadeus , can class declarations be 'chained' like var statements?

[amadeus]

I assume you mean like:

var ClassVar = class {};

If so, yes, that is valid JS

[bounceme]

no, like multiple class declarations seperated by commas

[amadeus]

So like:

class Test1 {}, class Test2 {};

If so, no, that is not valid JS, you will get a syntax error on the ,.

[bounceme]

and this?

class Test1 {},
Test2 {};

[bounceme]

chrome dev tools views it as an error at least

[amadeus]

Yeah, that's now allowed. Think of a class definition like named functions:

class Durp {}
function Durp(){}

They follow the same types of rules - like when you do a named function WITHOUT a var, a ; is not necessary

[bounceme]

this is ready!

[bounceme]

any objections?

[amadeus]

Can you squash the commits into one commit? Or at least edit the commit messages to be a bit more descriptive? Otherwise, I am good with this.