-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
runtime(vim): Improve :let-heredoc syntax highlighting #12923
runtime(vim): Improve :let-heredoc syntax highlighting #12923
Conversation
Codecov Report
@@ Coverage Diff @@
## master #12923 +/- ##
==========================================
- Coverage 82.20% 82.04% -0.17%
==========================================
Files 160 160
Lines 196942 194679 -2263
Branches 44128 43696 -432
==========================================
- Hits 161893 159719 -2174
+ Misses 22138 22087 -51
+ Partials 12911 12873 -38
Flags with carried forward coverage won't be shown. Click here to find out more. |
2aba0ec
to
da55133
Compare
@cecamp please |
"trim" and "eval" are allowed in any order and whitespace is not required after "=<<".
da55133
to
dbef1e3
Compare
I think this can be included @chrisbra, it's an isolated change. |
thanks, makse sense to include |
runtime(vim): Improve :let-heredoc syntax highlighting (vim/vim#12923) "trim" and "eval" are allowed in any order and whitespace is not required after "=<<". vim/vim@9358b8d Co-authored-by: dkearns <dougkearns@gmail.com>
runtime(vim): Improve :let-heredoc syntax highlighting (vim/vim#12923) "trim" and "eval" are allowed in any order and whitespace is not required after "=<<". vim/vim@9358b8d Co-authored-by: dkearns <dougkearns@gmail.com>
"trim" and "eval" are allowed in any order.
@cecamp, I sent this to you about a year ago but didn't receive a reply. This is unusual so I'm submitting the change here as well in case my email has dissipated in the ether.