-
Notifications
You must be signed in to change notification settings - Fork 64
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
Twig commentary #28
Comments
It looks like you can use vim-commentary's setting to change the comment behavior: https://github.com/tpope/vim-commentary#faq |
I have tried that but it prefixes the line with # giving: # .... comment here .... Which is not valid commentary :/ |
I think you need to change that line to include the correct comment, so
include {# #} in your vin configuration
…On Wed, Jul 15, 2020 at 03:20 Ahmed El Moden ***@***.***> wrote:
I have tried that but it prefixes the line with # giving:
# .... comment here ....
Which is not valid commentary :/
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#28 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADOHBOCOEGJ2VUISZRZPRLR3VKC3ANCNFSM4OWMCEAA>
.
|
@Herz3h This is what you want: autocmd FileType jinja setlocal commentstring={#\ %s\ #} |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm using this plugin for twig tempaltes which are very similar to jinja ones. But I struggle to use vim-commentary (tpope's plugin) with twig template. When I type
gcc
(to comment a single line):Consider this example:
Cursor being at second line, pressing gcc, preprends
##
to the line and give this result:Which is not valid syntax for twig file, instead it should use
{# .... comment here .... #}
How do I change this behavior ?
The text was updated successfully, but these errors were encountered: