dotfiles
neoterm
Our great sponsors
dotfiles | neoterm | |
---|---|---|
1 | 22 | |
4 | 1,287 | |
- | - | |
5.0 | 1.2 | |
3 months ago | about 1 year ago | |
Python | Vim Script | |
Apache License 2.0 | 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.
dotfiles
-
Vim 9.0 Was Released
I've spent so much time on configuring my (Neo)vim over the years I wouldn't even be able to estimate it (here it is if you're curious: https://github.com/kirillbobyrev/dotfiles/tree/main/.config/...).
The most important ones lately seem to be the LSP integrations (basically IDE features like autocompletion, go-to-definition etc) and auto-completion managers. But honestly it's been breaking all the time over the last year or so that I code more often in VSCode and maybe it's about time I stop trying to make an ever-improving IDE out of Neovim :(
Neovim project's direction seems to be aligned with making it easier to have IDE-like experience with LSP integration but it's been painful in Neovim. In Vim, it's typically even worse and even harder to set it up.
Overall, I've been using Vim for about 8 years and went from a really simple set-up of "this is just a text editor" down the IDE rabbit hole. I also went for Vim -> Neovim -> Vim -> Neovim and eventual split of the two configs in the end and. I'm thinking about making it much simpler again :D
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?
colorschemes - colorschemes for Vim
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
dotfiles - :metal: My collection of dotfiles for neovim, tmux, etc
vim-slime - A vim plugin to give you some slime. (Emacs)
dotfiles
vim-repl - Best REPL environment for Vim
kickstart.nvim - A launch point for your personal nvim configuration
iron.nvim - Interactive Repl Over Neovim
original-bsd - Original BSD history converted from CSRG's SCCS repository to Git (via SVN)
vim-floaterm - :computer: Terminal manager for (neo)vim
dotfiles - The configuration files (dotfiles) that I use on my computer (linux). It includes Vim, Zsh
deol.nvim - Dark powered shell interface for NeoVim/Vim8