The fold markers were unmaintained anyway and hence not working. No
folding is better than broken folding, and setting nothing allows user
configs such as language syntax based folding to work properly.
Not only is the list hopelessly out of date, it's almost impossible to
keep it up to date in any balance way. The only reasonably thing I could
think to put here would be a normalized list of authors scrapped from
git commit history, but Github's view of that is nicer anyway.
The days when vim plugins were distributed as individual files are long
gone, these days they are almost always git repositories or tarballs. As
such the relevant meta data is included, just not in this way. Not only
does this information have a habit of being absurdly out of date, it's
not really useful any more to try to update it.
Closes#415
While Markdown doesn't officially have a comment syntax, HTML comments
are widely parsed as such. This is what most Markdown treat as Markdown
comments. As a Markdown derivative it seams logical to do the same thing
in Rmarkdown.
The previously added '#' syntax seems to be for inside code blocks, and
that would be language dependent anyway. I've left the hash option as
the alternate.
See https://github.com/preservim/nerdcommenter/issues/400
Old URLs will continue to work for the foreseeable future since Github
forwards them, but new users in particular should be encouraged to use
the new org namespace when installing the plugin.
Coccinelle is a tool used for transforming C source code. It
uses the Semantic Patch Language (.cocci files) for doing this.
The conventional notation for commenting in semantic patches
is "//".
Used in conjunction with this plugin:
https://github.com/ahf/cocci-syntax
The cocci filetype is set, following which NERD_commenter can
be used in .cocci files.
Signed-off-by: Jaskaran Singh <jaskaransingh7654321@gmail.com>
- Sentinel is a new language developed by Hashicorp
- Sentinel supports three types of comments, `#` and `//` for single
line comments and `/* ... */` for multi-line comments as described
in their documentation - https://docs.hashicorp.com/sentinel/language/spec/#comments
- Since sentinel and terraform, .tf extension, are related, the `#`
symbol was chosen to keep in line with the tf single line comment
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
