vim9jit
neoterm
vim9jit | neoterm | |
---|---|---|
14 | 22 | |
498 | 1,287 | |
- | - | |
6.0 | 1.2 | |
about 2 months ago | about 1 year ago | |
Rust | 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.
vim9jit
-
Vim-writegood: nothing, but a simple Vim9 wrapper around write-good.
That's not happening any time soon, but there's this project by one of Neovim's contributers that transpiles Vim9 script into Lua.
-
Introducing neovim config written in C
Probably feasible with https://github.com/tjdevries/vim9jit actually
-
Has anyone migrated their vimrc to vim9script ?
There's https://github.com/tjdevries/vim9jit. It has reportedly been used to port Vim9script runtime files to Neovim.
- Vim9jit: A vim9script to Lua transpiler written in Rust
-
What does emacs and elisp has as an advantage over nvim and lua?
Neovim is going to use a transpiler that covers vim9script code to lua code using the nvim api in the future (https://github.com/tjdevries/vim9jit)
-
Any Vimscript to Lua transpilers?
I didn’t watch the streams because I wasn’t totally sure what he was even doing, but maybe this will take some of it off your hands: https://github.com/tjdevries/vim9jit
-
I am done with vim (ThePrimeagen)
It could (rightly) be argued that neovim could just merge in vim9script, but I think this probably isn't the best more. I'm personally more in favor of getting a vim9 cross-compiler working, that way there's an easy way to support both. But that's my ignorant two cents on the matter.
-
So, is your main editor Vim or Neovim?
A core contributor to Neovim is toying with a Vim9Script to Lua convertor.
-
Vim 9.0 Was Released
That's not necessarily true.
Core maintainer of the Neovim Tjdevries is working on a compatibility layer that would allow vim9 to not only run in Neovim, but likely faster.
Source: https://github.com/tjdevries/vim9jit
-
Vim 9 has been released
My understanding was the neovim folks decided this wasn't work the hassle. TJ already has https://github.com/tjdevries/vim9jit, which transpiles vim9scripts to lua, and that is much more likely the way things will go.
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?
vim-startuptime - A plugin for profiling Vim and Neovim startup time.
toggleterm.nvim - A neovim lua plugin to help easily manage multiple terminal windows
lua-languages - Languages that compile to Lua
vim-slime - A vim plugin to give you some slime. (Emacs)
vim9 - An experimental fork of Vim, exploring ways to make Vim script faster and better.
vim-repl - Best REPL environment for Vim
nvim - Straightforward and pure Lua based Neovim configuration for my work as DevOps/Cloud Engineer with batteries included for Python, Golang, and, of course, YAML
iron.nvim - Interactive Repl Over Neovim
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
vim-floaterm - :computer: Terminal manager for (neo)vim
impatient.nvim - Improve startup time for Neovim
deol.nvim - Dark powered shell interface for NeoVim/Vim8