vim-dadbod VS neoterm

Via dadbod

I used dadbod[0] and the following in my vimrc[1] to do a similar thing, only I haven't make the shortcuts for sending a block yet.

Looks nice though, maybe I'll try it out sometime!

[0] https://github.com/tpope/vim-dadbod

[1] au FileType sql nmap d :%:DB g:db

Maybe that helps with autocompletion in dadbod: ```lua Plug 'https://github.com/tpope/vim-dadbod.git' Plug 'https://github.com/kristijanhusak/vim-dadbod-ui.git' Plug 'https://github.com/kristijanhusak/vim-dadbod-completion.git'

Check out these two: https://github.com/tpope/vim-dadbod/ https://github.com/kristijanhusak/vim-dadbod-ui

I used dadbodUI for viewing table, before you install dadbodUI, remember to install dadbod https://github.com/tpope/vim-dadbod

There is a plugin for connecting to DBs [0] and others built upon it, a UI [1] and even completion [2].

[0] https://github.com/tpope/vim-dadbod

I use Vim with neoterm, highly recommend. - guaranteed support on everything with a repl - never creates unexpected windows - every interaction is explicit

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.

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.

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)

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.

I've been using Neoterm, coupled with its vim-test strategy, for this

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)

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.

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

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.