kcov
nvim
kcov | nvim | |
---|---|---|
19 | 5 | |
683 | 85 | |
- | - | |
8.8 | 9.5 | |
5 days ago | 3 days ago | |
C++ | Lua | |
GNU General Public License v3.0 only | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
kcov
- kcov: NEW Data - star count:590.0
-
The first 6 months of a self-hosted compiler
Logically after the 24 of January the rate felt very low, but not to zero. Styx backend supports emiting of DWARF debug informations and they can be used by tools to produce coverage reports. In particular I used kcov, which produces nice html output but also cobertura-style reports that are compatible with CodeCov.
-
neotest: A modern, powerful testing plugin
Did you look into kcov yet? https://github.com/SimonKagstrom/kcov
- kcov: NEW Data - star count:579.0
nvim
-
Neovim lua setup. Init.lua, plugin/, after/plugin folders
Hmm... It should be. Here is my setup and I use both 'init.lua' and 'after/ftplugin'. The latter is sourced every time filetype option is set.
-
Usage of 'after/ftplugin' directory for filetype-specific configuration
This is meant as a Friday post to make more people aware of 'after/ftplugin' directory, because I find this approach really more structured than using autocommands. For reference, here is how I do it.
-
neotest: A modern, powerful testing plugin
It is in "closed alpha", so to speak, i.e. in my Neovim configuration [here](https://github.com/echasnovski/nvim/blob/master/lua/mini-dev/test.lua). Yet needs some Lua experience to go through source code, but it will be easier with more examples in the near future. I plan to release it for beta testing in a couple of weeks.
-
'mini.surround' new features: custom surroundings and search method
Sure, here you go.
-
Advice for r and rmarkdown using vim?
Hi, I use Neovim with R and Rmarkdown without Nvim-R for a quite a while now. Here is my config.
What are some alternatives?
neotest - An extensible framework for interacting with tests within NeoVim.
cpp-project - Boiler plate template for C++ projects, with CMake, Doctest, Travis CI, Appveyor, Github Actions and coverage reports.
neotest-rspec - ๐งช Neotest adapter for RSpec. Works in Docker containers too
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
nvim-dap - Debug Adapter Protocol client implementation for Neovim
languageserver - An implementation of the Language Server Protocol for R
coverde - A set of commands for coverage trace files manipulation.
nvim-dap-ruby
ModernCppStarter - ๐ Kick-start your C++! A template for modern C++ projects using CMake, CI, code coverage, clang-format, reproducible dependency management and much more.
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler