Fujiwara Takuya
Fujiwara Takuya
If neovim thankfully uses our idea of metainfo repository, please see the [overview image](https://github.com/vim-vivacious/metainfo/issues/1#issuecomment-178585193). The image is totally written in English because we suppose a workflow which is a part...
Well, also I thought that like "well, vim-pi seems enough for me" until I talked with @Shougo. According to [his story](https://github.com/vim-vivacious/metainfo/issues/1#issuecomment-170244209), ### 1. Plugins that does not exist are listed...
The image is just an overview and we are just starting to work on that. So please tell me if the overview is ambiguous. And no codes are available yet......
@Shougo I see. Indeed it seems a little bit old.
@cweagans > Crawling Github repos is not a valid approach Yes. We also talked about that and the bot does not have to crawl GitHub repositories via GitHub API. We...
## Where Vim9 script is enabled By @thinca - Look up `:vim9s[cript]` at the beginning of file - Between `:def ... :enddef` - `command Foo { ... }` - `autocmd...
Sorry, I couldn't clearly understand what you said. 日本語でいいですよ〜 いくつか質問があるのですが、以下がちょっと曖昧で良く分かりませんでした。 * 問題は現在も再現し続けているのか？ * 以下の意味がよく分かりませんでした > b:undo_ftplugin execute manually, need clearing in b:undo_ftplugin ?
`NERDCommenterToEOL` is same as #43 behavior? `NERDCommenterSexy` seems interesting. I'll add the feature.
Update title and body. Before: More intelligent comment action After: 'gcc' Mapping: Detect `(caw:a:...)` comment
Simplify comment.