Note that to-date there has not been an official vim filetype for
React-Javascript and React-Typescript. The `javascriptreact` and
`typescriptreact` filetypes were added upstream to both Vim (8.1.1890)
and NeoVim during the course of discussion on this PR.
Some other Vim plugins are known to use filetype hacks such as
`javascript.jsx` or `typescript.jsx`. This plugin supports the now
official upstream designations. If this conflicts with your usage you
can either tweak the other plugins (and/or submit a fix to use the
official filetypes upstream) or add custom file type comment setting in
your vim rc/init file.
Co-Authored-By: Caleb Maclennan <caleb@alerque.com>
11 years ago, b54d3bb renamed NERDCom[A-Z] mappings to <plug>NERDCommenter[A-Z] mappings. But, the docs were never updated. When README.md was later created, it kept the old NERDCom[A-Z] names.
Split tag NERDComAlignedComment and use new form NERDCommenterAlign{Left,Both}
Update other help tags from NERDCom[A-Z] pattern to NERDCommenter[A-Z]
I can't find any record of this being a legitimate filetype. It isn't in
vim or nvim's filetype detection system and nothing comes up in search.
If it's legit somebody can complain and we'll add it back, but it seems
likely this was left over from a fat-fingered mistake during the initial
development of the plugin.
Fixes#363
Closes#279
Since original author of this PR has deleted their Github account
I squashed their two commits and added one to fix the issue with the
implementation as noted in the PR.
This adds support for shader_test files in piglit, the open source
test suite for OpenGL implementations such as mesa. More information on
piglit can be found at:
https://piglit.freedesktop.org/
This reverts commit 0e1f6f6866.
Given the unexpected behaviour of this and disruption to people's
established work flows, I'm reverting this until a better solution can
be found that only handles the special comment format inside React code
blocks.
Technically the minimum necessary syntax for block comments requires
only a single hyphen (`-}`, `{-`), but I have found that using a double
hyphen plays a bit more nicely with the elmcast/elm-vim auto-formatting.
Further, uncommenting when using the single dashes leaves an extra level
of indentation (again, when using elmcast/elm-vim).
M4 knows about two types of ignoring text. But the concept which the
GNU M4 manual refers to as "comments" [0] (i.e., lines prefixed with
hash signs) is actually telling the interpreter "ignore this text, but
pass it to the output". Most of the time, people don't want the macro
comments in their output, so instead the `dnl` ("discard to next line")
macro [1] is usually used for comments in the document-my-thoughts
sense.
[0]: https://www.gnu.org/software/m4/manual/m4.html#Comments
[1]: https://www.gnu.org/software/m4/manual/m4.html#Dnl
Previously the `NERDTrimTrailingWhitespace` option was only evaluated when uncommenting a line. However sometimes trailing whitespace was being added when commenting, notably when commenting empty lines. This checks for and removes such space at comment time.
