nvim
neoterm
nvim | neoterm | |
---|---|---|
5 | 22 | |
85 | 1,287 | |
- | - | |
9.5 | 1.2 | |
3 days ago | about 1 year ago | |
Lua | Vim Script | |
MIT License | GNU General Public License v3.0 or later |
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.
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.
neoterm
-
Does anyone use vim for lisp dev?
I use Vim with neoterm, highly recommend. - guaranteed support on everything with a repl - never creates unexpected windows - every interaction is explicit
-
mini.move - Move any selection in any direction
At the moment I am planning to write two modules and then start on 'mini.terminals'. I usually prioritize work based on combination of "I have some cool idea about this" and "I don't like what I am currently using". I am using kassio/neoterm for a very long time and it is quite OK for my needs.
-
What is to go-to environment on Windows for Common LISP development?
Neovim works just fine. I use Neoterm to send-to-repl, here's what my config looks like. Your other options include vlime and slimv. I switched to neoterm because it's simple, explicit, and doesn't create unpredictable windows. Works for any other language just as well.
-
Show HN: PostgreSQL Sessions in Vim
Using neovim + https://github.com/kassio/neoterm I have a similar, possibly simpler, workflow that doesn't require any other program (especially listening willy nilly with no authentication/authorization whatsoever) other than your normal SQL client running:
* I open a :Term window, in which I run the sql client (i.e. ":Texec sqlite\ foo.sqlite" or ":Texec mysql foo", etc)
-
Is SLIME setup possible for Vim?
I'm using neoterm. I like that I can use the same tech for every language + consistent keybinds. Also Slime might not support a more fringe or outdated lisp distro but a plain old VTY terminal always will.
-
How to automatically close or re-use previous terminal when running vim-test multiple times
I've been using Neoterm, coupled with its vim-test strategy, for this
-
Vim 9.0 Was Released
Having gone from a stock vim to a highly modified vim and back again, here are some plugins that I find really boost my productivity:
- neoterm, for opening a REPL in a split buffer and quickly sending chunks of lines to the REPL (https://github.com/kassio/neoterm)
- fzf for faster buffer and file navigation (https://github.com/junegunn/fzf.vim)
- vim fugitive for good git integration (https://github.com/tpope/vim-fugitive)
- some other tpope plugins (surround, unimpared, commentary, vinegar)
-
What would you consider a modern lisp workflow/toolchain?
I found Vlime to be more updated than slimv and give a smoother experience. With time I've switched to bare neoterm which I highly recommend. CL and lisps in general are designed with a text repl in mind, so this is the method that is guaranteed to work on every obscure CL distribution, and also transfer well to any other REPL-based languages.
-
Any way to send errors from npm (yarn) local server to neovim?
I start terminal inside of neovim. It works really well. In this terminal, you can use gf (goto file) keybindigs, etc. It works especially well with this plugin: https://github.com/kassio/neoterm
-
Advice for r and rmarkdown using vim?
Workflow is basically to open two windows (left with code, right with terminal) and send code from left window to right with a help of kassio/neoterm.
What are some alternatives?
neotest - An extensible framework for interacting with tests within NeoVim.
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
neotest-rspec - 🧪 Neotest adapter for RSpec. Works in Docker containers too
vim-slime - A vim plugin to give you some slime. (Emacs)
NvChad - Blazing fast Neovim config providing solid defaults and a beautiful UI, enhancing your neovim experience.
vim-repl - Best REPL environment for Vim
languageserver - An implementation of the Language Server Protocol for R
iron.nvim - Interactive Repl Over Neovim
nvim-dap-ruby
vim-floaterm - :computer: Terminal manager for (neo)vim
refactoring.nvim - The Refactoring library based off the Refactoring book by Martin Fowler
deol.nvim - Dark powered shell interface for NeoVim/Vim8