-
Notifications
You must be signed in to change notification settings - Fork 102
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
Support for Vue file #176
Comments
This change posva/vim-vue#42 seems to have taken care of it. It works for me now. |
I'm sorry I totally missed out on this issue. Since it seems to be fixed in vim-vue, I'll close this issue. |
We decided to revert the I can make a pull request to support this again. |
This would be very much appreciated. Thanks! |
My vue files work fine for the most part except for when I'm using
After line-commenting on
After line-commenting on the commented line...
So it looks like it is using the default filetype |
So it looks like it is using the default filetype |commentstring| once,
but then switching to the context-aware |commentstring| if I'm
commenting an already-commented line...?
If you have the current head version of tcomment installed, please read
`:h tcomment-debug`, place the cursor at the position in question and
`:call tcomment#debug#CollectInfo()`. If you use an older version,
please use
echom 'TCOMMENT: &ft =' &filetype
echom 'TCOMMENT: ft =' tcomment#filetype#Get()
echom 'TCOMMENT: stx =' tcomment#syntax#GetSyntaxName(line('.'),
col('.'))
echom 'TCOMMENT: ct =' string(tcomment#GuessCommentType())
And post the result here. Thanks!
|
Here is the requested output:
|
Sorry for not having tested that. Is this the result from this?
I would expect the "<!--" to have some unexpected syntax name. |
My first post was the output from:
For this:
The output is:
In both cases the cursor is positioned on the first character of the middle line. |
stx = pugHtmlConditionalComment
Since the comment definition for the pug filetype is
call tcomment#type#Define('pug', '//- %s')
This should result in
//- <!-- div -->
You'd expect to uncomment the comment though.
Where is pugHtmlConditionalComment used in the document? Does your
plugin somehow distinguish between normal html comments and pug
conditional comments -- whatever that is. Or are the all just comments?
I don't know pug.
|
I'm not the author of the
And indeed, tcomment correctly works just like this in a standalone
The issue is that the behavior is for some reason different inside a |
The
.vue
have multiple format in itjavascript, html and css
, to make matter worse it also support preprocessorjade, pug, stylus, sass
on the very same file.What I got for comment only html comment
<!-- -->
There is issue opened in posva/vim-vue (for multiple syntax highlighting) which address the same problem posva/vim-vue#17
Maybe something can be worked out
The text was updated successfully, but these errors were encountered: