Our great sponsors
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
xxh
🚀 Bring your favorite shell wherever you go through the ssh. Xonsh shell, fish, zsh, osquery and so on.
fzf https://github.com/junegunn/fzf.vim
coc https://github.com/neoclide/coc.nvim or deoplete
fugitive https://github.com/tpope/vim-fugitive or tig https://github.com/codeindulgence/vim-tig
fugitive https://github.com/tpope/vim-fugitive or tig https://github.com/codeindulgence/vim-tig
and prettier https://github.com/prettier/vim-prettier
May be heresy to say in here, but running Doom Emacs locally would probably be more pleasant than any of the other options. You can use TRAMP to edit remote files without laggy input or having to build your dev env remotely.
My ~/.vim/ is a Git repository and I make it support older versions of Vim by checking for the existence of features before using them, because I couldn't stand my .vimrc emitting any errors on Vim startup. If you're interested, it's here: https://github.com/mgedmin/dotvim/
I recommend a colorscheme that works well at multiple levels (88-color/ 256-color) and is set up to look almost the same in remote terminal vim as it does in gvim - personal favorite is ciaranm's "Inkpot"