Skip to content

Develop -> Master #442

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

Merged
merged 43 commits into from
May 27, 2016
Merged

Develop -> Master #442

merged 43 commits into from
May 27, 2016

Conversation

amadeus
Copy link
Collaborator

@amadeus amadeus commented May 25, 2016

Just another base release. I kinda want to get this out soon though, so we stop getting those bug reports regarding the lookbehind limiters.

bounceme and others added 30 commits April 25, 2016 19:53
also now that I know about cindent i'm curious if there are other places like this to remove code and increase performance
Fix class definitions with no name
This ES6 version of jsFuncName requires some special handling to not, by
default, overwrite jsObjectKey and also not overwrite jsFuncCall.
Custom jsFuncName for object definitions
I am commenting this out since I am working through a better
implementation.
* Update javascript.vim

* Update javascript.vim
proper asi for control statements
Will need to better fix this soon, just getting this hotfix out asap
Temporary fix for older versions of vim
* c style opening curly braces

#68

* Update javascript.vim
Prevent limited lookbehinds in older vers of vim
this doesn't change any behavior it is just for clarity
* Update javascript.vim

* Update javascript.vim
should be considered last non whitespace non comment
also I'm removing all the template string indentation, will leave it as a comment if someone can justify actually changing a string
should have said more bugs #432
this should be working now
also added a modeline to fold away the gq code
bounceme and others added 6 commits May 17, 2016 17:11
* random fixes and improvements

this also removes the parentheses alignment, we can leave it in I suppose, but I'd like to revisit that later. if anyone objects please let me know.this needs to be cleaned up a bit before merging

* Update javascript.vim

* Update javascript.vim

* Update javascript.vim
This class regex will match if the text class is contained within a
larger variable name, and therefore is broken.
Forcing `class` text to be a keyword
regexes have been cleaned and no longer have ruby specifics. all of the regex matching has been either refactored to use the s:match function if it is needed to look at the syntax of the characters, or changed to be a simple match to save performance.the current file has none of the bugs i talked about that were caused by the last commit
another tiny commit, this is just fix which for a small bug that slipped past me
* wrapping comments improved

this improves most regexes and the prevnonblanknonstring function
@davidchambers
Copy link
Collaborator

Let's do it. :)

this is just a more correct, thorough check, for multiline comments
@bounceme
Copy link
Collaborator

the indent script is ready for a merge

@amadeus
Copy link
Collaborator Author

amadeus commented May 25, 2016

i added a small issue I noticed in #443, is that an easy fix? If so, I'd like to get that in first, otherwise we can hold off and fix later.

@bounceme
Copy link
Collaborator

hmm, I'm at work. I'll try and fix it soon

@bounceme
Copy link
Collaborator

actually, since we use cindent for multiline comments, this is probably customizable. maybe in the cinoptions section of the vim help you can find it

@bounceme
Copy link
Collaborator

cN    Indent comment lines after the comment opener, when there is no
          other text with which to align, N characters from the comment
          opener.  (default 3).  See also |format-comments|.

        cino=             cino=c5
          /*                /*
             text.           text.
           */                */

@amadeus
Copy link
Collaborator Author

amadeus commented May 25, 2016

Ok cool, then I think we can just go ahead and merge this, and I'll worry about that later.

bounceme and others added 6 commits May 26, 2016 00:20
this fixes some serious issues with the way a continuation is detected and also removes the specific code for comma first style,which was very breakable
a comma should be considered an operator
* change the regex engine according to warning
the readme won't tell the user to change the regexpengine now that the correct one is set
Shebang doesn't have to contain env
@amadeus
Copy link
Collaborator Author

amadeus commented May 27, 2016

Alright, I think this may be good to go?

@amadeus amadeus merged commit 0f0e4a7 into master May 27, 2016
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

Successfully merging this pull request may close these issues.

4 participants