Kim 金可明

@dbatten5 I've done a big upgrade with all the parsers today and have published [v3.12.0](https://github.com/kkoomen/vim-doge/releases/tag/v3.12.0). Please upgrade locally and test whether or not you still have any issues.

@khoint0210 Ah yes, you did run a local build last time, which has precedence over the actual built binary file. I suggest you to remove the `bin` folder and run...

@dbatten5 See my previous comment in order to properly confirm whether or not it works.

@resolritter Sorry for the terribly long response. At the time you've submitted this issue I did have a look around and asking around as well for better alternatives. The best...

@resolritter If you're using vim (not neovim, but just vim) you can use the following config for vue files: ```vim let g:doge_filetype_aliases = { \ 'javascript': ['vue'] \} ```

@scottbolte Hi, thanks for your suggestion! I've created a PR with passing tests etc that I want you to have a look at. If you approve, place a comment at...

@scottbolte let's continue this discussion at the PR.

I can add a python-specific option for this later. I'm super busy lately, so please be patient. I'll try to implement this whenever I have time.

Hi, I did have this version before I released DoGe publically and it worked well, yet there is no possibility to support every language I am currently supporting. The problem...

Sorry that this is still not fixed. The problem I'm having is that I should be able to merge two multiline strings (doc blocks) together using a history algorithm that...