asyncrun.vim VS Bear

Compare asyncrun.vim vs Bear and see what are their differences.

asyncrun.vim

:rocket: Run Async Shell Commands in Vim 8.0 / NeoVim and Output to the Quickfix Window !! (by skywind3000)

Bear

Bear is a tool that generates a compilation database for clang tooling. (by rizsotto)
Our great sponsors
  • InfluxDB - Power Real-Time Data Analytics at Scale
  • WorkOS - The modern identity platform for B2B SaaS
  • SaaSHub - Software Alternatives and Reviews
asyncrun.vim Bear
27 50
1,808 4,352
- -
7.2 5.4
6 days ago about 1 month ago
Vim Script C++
MIT License GNU General Public License v3.0 only
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
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.

asyncrun.vim

Posts with mentions or reviews of asyncrun.vim. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-05-03.

Bear

Posts with mentions or reviews of Bear. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2023-06-17.
  • Eglot + clangd not working for NetHack code base
    3 projects | /r/emacs | 17 Jun 2023
    An update: I am now able to make everything work by generating `compile_commands.json` using compiledb. I'm aware that there is another tool Bear but for some reason it generates an empty `compile_commands.json` file for me.
  • New User C Setup Help?
    4 projects | /r/neovim | 24 May 2023
    Regarding the libraries, you might need to add it to clangd’s configuration. A convenient way is to have a compile_commands.json in your project (this is generated by some build tools like CMake, but if you don’t use them, have a look at bear).
  • vscode alternative for C++ on M1 mac?
    4 projects | /r/cpp | 15 May 2023
    Note that you need to have a compile_commands.json file. That file can easily be generated by CMake, Meson, etc. For other build systems checkout Bear https://github.com/rizsotto/Bear
  • I hope that cscope can make a comeback in the versions after 0.9
    2 projects | /r/neovim | 8 Apr 2023
    make a 'gcc' command/executable that do nothing and make it first in your PATH and then run bear with make: https://github.com/rizsotto/Bear/issues/219 It is unfortunate that bear doesn't catch the output of the make command with '--dry-run' as it still prints the compile commands, it seems not that hard to support this and I think many ppl would benefit..
  • Is CMake necessary to set up a C++ "IDE" in neovim?
    4 projects | /r/neovim | 17 Mar 2023
    But it sounds like maybe you’re assuming for the purposes of using something like clangd (highly recommended for coding in cpp projects in general, you want to be using this in vscode or whatever else anyway, codelion notwithstanding I suppose) with neovim on a c++ project that you have to use cmake to produce a compilation database to use with neovim plugins (e.g. clangd via nvim-lsp et. al.). In this case, be aware that the https://github.com/rizsotto/Bear tool is a handy way to just tack it on to whatever command you’re using to run a c++ code build step, and it will give you a compile_commands.json, corresponding to the compiler commands it invoked, on a silver platter.
  • Makefile versus CMake build system
    3 projects | /r/embedded | 8 Mar 2023
    I guess your questionmarks are about installing "bear", he refers to this project: https://github.com/rizsotto/Bear
  • Mason LSP Not Detecting Header Files
    2 projects | /r/neovim | 4 Feb 2023
    You can use bear in order to generate compile_commands.json on compilation and make the errors disappear.
  • Clangd header files not found
    2 projects | /r/neovim | 4 Jan 2023
    I'd also recommend to use bear which helps clangd to find the header files and stuff if something doesn't work correctl.
  • The state of neovim with Unreal 4/5
    2 projects | /r/neovim | 27 Dec 2022
    Have you tried it with bear to create the compile_commands.json file?
  • Help a Linux kernel dev setup LSP
    8 projects | /r/emacs | 18 Oct 2022
    Both servers need a compilation database compile_commands.json in order to populate and read symbols and locations, as well as flags and configurations. Some build generators like CMake and Meson are able to produce these files (cmake . -DCMAKE_EXPORT_COMPILE_COMMANDS=1 for the first and automatically for the latter). If you aren't using such a system and using, for example, plain Makefiles, you will need a tool like Build EAR to produce the compilation database.

What are some alternatives?

When comparing asyncrun.vim and Bear you can also consider the following projects:

compiledb - Tool for generating Clang's JSON Compilation Database files for make-based build systems.

vim-dispatch - dispatch.vim: Asynchronous build and test dispatcher

vscode-cpptools - Official repository for the Microsoft C/C++ extension for VS Code.

NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.

scan-build - Clang's scan-build re-implementation in python

coc-clangd - clangd extension for coc.nvim

clangd - clangd language server

ccls - C/C++/ObjC language server supporting cross references, hierarchies, completion and semantic highlighting

vscode-cmake-tools - CMake integration in Visual Studio Code

lsp-zero.nvim - A starting point to setup some lsp related features in neovim.

doom-nvim - A Neovim configuration for the advanced martian hacker [Moved to: https://github.com/doom-neovim/doom-nvim]

fzf-lua - Improved fzf.vim written in lua