asyncrun.vim
Bear
Our great sponsors
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 |
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
-
Is there a plugin for async shell :%!command ?
I'm familiar with asyncrun.vim, but it outputs as quickfix. I specifically want to filter editor text (as stdin/stdout).
-
When creating a new window, can you open to the CWD in your terminal emulator of choice?
If you want to open a new terminal in the CWD of neovim, you couls either use neovim's built in terminal or, if it needa to be kitty, use the neovim AsyncRun-plugin and start kitty with the necessary command-line options to start in neovims's CWD(I uae this with Alacritty instead of Kitty).
-
How do you handle level productivity: autoformat, insert debug statement, execute file?
For running the file there are several tools. I have been using asynctasks.vim which is built on top of asyncrun.vim which I usually use to open a tmux pane and run the code/test. I've been looking at switching to overseer.nvim but haven't yet. I use justfiles to define all of my tasks.
-
How do you guys run the code you write with vim?
I can :Man blah to look up docs or :AsyncRun to build/run with jumpable output in the quickfix. Doing it within vim means I can pull from any register for pasting, yank without a mouse, hide buffers or move them to tabs, etc.
-
VSCode -> VIM, but how do I accomplish the other IDE tasks?
I use asyncrun.vim to see compile output as it happens (line by line instead of the whole dump when compile completes) and asynchronously (so I can keep navigating around).
-
Run code with F5 and leave buffer open
Also AsyncRun and AsyncTasks worth a mention.
-
Asyncrun and ANSI codes
Hey folks, I'm using asyncrun to run async commands on vim, but some of them output ansi colorcodes, I've found powerman's AnsiEsc which is able to conceal and highlight them very well, but that only work for the current buffer, so there's no way to automate it from g:asyncrun_exit and I can't set the -post from asynctasks, has anyone found a way to fix this?
- Run code in Nvim
-
Run Any Language with Same Macro!
As you can see, I use asyncrun.nvim since sometime compiling/running will take quite long. For some complex situations, like c++ project with cmake, I use following code:
-
Run external commands in background
Recently I came across AsyncRun, a plugin that handles that. https://github.com/skywind3000/asyncrun.vim
Bear
-
Eglot + clangd not working for NetHack code base
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?
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?
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
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?
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
I guess your questionmarks are about installing "bear", he refers to this project: https://github.com/rizsotto/Bear
-
Mason LSP Not Detecting Header Files
You can use bear in order to generate compile_commands.json on compilation and make the errors disappear.
-
Clangd header files not found
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
Have you tried it with bear to create the compile_commands.json file?
-
Help a Linux kernel dev setup LSP
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?
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