asyncrun.vim
vim-rooter
asyncrun.vim | vim-rooter | |
---|---|---|
27 | 24 | |
1,820 | 1,190 | |
- | - | |
7.2 | 4.4 | |
about 1 month ago | 10 days ago | |
Vim Script | Vim Script | |
MIT License | 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.
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).
-
Output of external command to messages ?
try asyncrun:
-
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:
vim-rooter
-
netrw made better
This or users may have monorepo style projects and vim-rooter to auto-set cwd to specific directories within the project based on certain file markers (e.g. makefile, package.json, ...etc), to accomplish something like :e dir1/file.go | make would run make and then :e dir2/file2.ts | make would run npm.
-
How to go up a directory while inside of telescope.nvim?
maybe you are already doing this and you want to access files outside the project directory but if not I use vim-rooter to set the root dir of the project automatically when I open vim
-
You don't need 'vim-rooter' (usually) or How to set up smart autochange of current directory
The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:
-
Vim Issue with opened buffer file location
It depends where you open vim. If you are in home and open a file (even in sub directories) like nvim directory/file.txt, uour vim's current working directory (aka cwd) will be home. A way to make this automatic I think is the built in autocd (or something like that) and plugins like vim-rooter.
-
How to stop Telescope from changing the root directory after opening a file?
An alternative would be using a plugin like vim-rooter : https://github.com/airblade/vim-rooter
- NvimTree - how to get this behaviour?
-
How to properly cd, so plugins pick up project root?
I just use rooter and avoid thinking about it...
-
How to automatically cd to the git root of the current buffer?
There's vim-rooter, which is great.
- Whenever I'm looking for plugins these days [OC]
-
What’s the best start up screen written in Lua?
No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.
What are some alternatives?
vim-dispatch - dispatch.vim: Asynchronous build and test dispatcher
project.nvim - The superior project management solution for neovim.
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
vim-startify - :link: The fancy start screen for Vim.
fzf-lua - Improved fzf.vim written in lua
nvim-bqf - Better quickfix window in Neovim, polish old quickfix window.
vim-fugitive - fugitive.vim: A Git wrapper so awesome, it should be illegal
nvim-spectre - Find the enemy and replace them with dark power.
asynctasks.vim - :rocket: Modern Task System for Project Building, Testing and Deploying !!
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
todoist.nvim - A todoist extension for neovim
replacer.nvim - A powerful refactoring tool for nvim.