-
-
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): Update base-syntax, match multiline continued comments #13936
Merged
chrisbra
merged 1 commit into
vim:master
from
dkearns:runtime-vim-match-multiline-comments
Jun 11, 2024
Merged
runtime(vim): Update base-syntax, match multiline continued comments #13936
chrisbra
merged 1 commit into
vim:master
from
dkearns:runtime-vim-match-multiline-comments
Jun 11, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dkearns
force-pushed
the
runtime-vim-match-multiline-comments
branch
3 times, most recently
from
January 31, 2024 13:58
770299e
to
7ea8b10
Compare
dkearns
force-pushed
the
runtime-vim-match-multiline-comments
branch
3 times, most recently
from
February 3, 2024 16:15
5f7a118
to
852e94a
Compare
dkearns
force-pushed
the
runtime-vim-match-multiline-comments
branch
from
March 21, 2024 14:24
852e94a
to
a58db2a
Compare
dkearns
changed the title
runtime(vim): Update syntax file - multiline strings
runtime(vim): Update base syntax file, match multiline continued comments
Jun 11, 2024
dkearns
changed the title
runtime(vim): Update base syntax file, match multiline continued comments
runtime(vim): Update base-syntax, match multiline continued comments
Jun 11, 2024
Match multiline (continued) line comments. Continued tail comments are not supported yet.
dkearns
force-pushed
the
runtime-vim-match-multiline-comments
branch
from
June 11, 2024 16:06
a58db2a
to
13ce1ee
Compare
Thanks! |
zeertzjq
added a commit
to zeertzjq/neovim
that referenced
this pull request
Jun 12, 2024
…continued comments (vim/vim#13936) Match multiline (continued) line comments. Continued tail comments are not supported yet. vim/vim@059cbe8 Co-authored-by: dkearns <dougkearns@gmail.com>
dkearns
added a commit
to dkearns/vim
that referenced
this pull request
Jun 12, 2024
Leading whitespace is no longer matched as part of the line comment as of vim#13936.
dkearns
added a commit
to dkearns/vim
that referenced
this pull request
Jun 12, 2024
Leading whitespace is no longer matched as part of the line comment as of vim#13936.
dkearns
added a commit
to dkearns/vim
that referenced
this pull request
Jun 12, 2024
Leading whitespace is no longer matched as part of the line comment as of vim#13936.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Match multiline (continued) line comments.
Continued tail comments are not supported yet.