3 ms·

There's much to say about "wasting" your off time by learning your editor. I still remember this one time, 15 years ago, where I spend literally the whole nigh

There's much to say about "wasting" your off time by learning your editor. I still remember this one time, 15 years ago, where I spend literally the whole night configuring my .vimrc, reading the :help pages for all of the configuring options, doing the tutorials, and just moving around and getting comfortable with it. At 8PM that night I didn't know Vim, but by 6AM the next morning I was very productive in it. I'd say about 80% of my productiveness with Vim was achieved that night, and I could never change to a non-Vi editor since.

mekster 4y ago
It's worth learning again what neovim offers with LSP and it's ecosystem. https://github.com/folke/trouble.nvim https://github.com/folke/trouble.nvim You'd appreciate nothing out of Typescript if your editor doesn't do LSP. AstroNvim gives you a good start.
- wruza 4y ago
  Feels like they all try to make vscode out of vim. Is there a truly vim-spirited LSP plugin? The one that doesn’t flicker on its own when you type, and only shows issues in quickfix after :make equivalent, even if it works asynchronously (works with Vim would also be great). I don’t mind configuring it for a week, but what’s on gif-shots usually repels me.
  - d12bb 4y ago
    Basically all you need is nvim-lspconfig, which just attaches the language servers to your buffers (so you wouldn't even need that, but it saves a lot of boilerplate). From there you can use all you already know (this is from my Lua-based config, but you can do the same in Viml): vim.keymap.set("n", "K", vim.lsp.buf.hover, { buffer = buf }) vim.keymap.set("n", "<leader>qf", vim.diagnostic.setqflist, { buffer = buf, desc = "Quickfix diagnostics" }) -- open Quickfix with LSP issues, Loclist possible too vim.api.nvim_buf_set_option(buf, "omnifunc", "v:lua.vim.lsp.omnifunc") -- use LSP completion for omnifunc vim.api.nvim_buf_set_option(buf, "tagfunc", "v:lua.vim.lsp.tagfunc") -- Ctrl+] for go to definition using LSP instead of ctags vim.api.nvim_buf_set_option(buf, "formatexpr", "v:lua.vim.lsp.formatexpr()") -- Code formatting (gq etc) using LSP Everything else one always sees with Neovim and LSP are other plugins like nvim-cmp or Telescope.
  - jeremija 4y ago
    I've been using ALE for years and even contributed to it: https://github.com/dense-analysis/ale https://github.com/dense-analysis/ale
vladvasiliu 4y ago
> I could never change to a non-Vi editor since. This isn't only good, though. Like you, when I don't use vim itself (or nvim nowadays) I use vim bindings in my IDE. But since I do most of my typing in this environment, I've lost track of the number of times I've closed windows by mistake because I have ^w in muscle memory...

mekster 4y ago

It's worth learning again what neovim offers with LSP and it's ecosystem. https://github.com/folke/trouble.nvim https://github.com/folke/trouble.nvim You'd appreciate nothing out of Typescript if your editor doesn't do LSP. AstroNvim gives you a good start.

wruza 4y ago
Feels like they all try to make vscode out of vim. Is there a truly vim-spirited LSP plugin? The one that doesn’t flicker on its own when you type, and only shows issues in quickfix after :make equivalent, even if it works asynchronously (works with Vim would also be great). I don’t mind configuring it for a week, but what’s on gif-shots usually repels me.
- d12bb 4y ago
  Basically all you need is nvim-lspconfig, which just attaches the language servers to your buffers (so you wouldn't even need that, but it saves a lot of boilerplate). From there you can use all you already know (this is from my Lua-based config, but you can do the same in Viml): vim.keymap.set("n", "K", vim.lsp.buf.hover, { buffer = buf }) vim.keymap.set("n", "<leader>qf", vim.diagnostic.setqflist, { buffer = buf, desc = "Quickfix diagnostics" }) -- open Quickfix with LSP issues, Loclist possible too vim.api.nvim_buf_set_option(buf, "omnifunc", "v:lua.vim.lsp.omnifunc") -- use LSP completion for omnifunc vim.api.nvim_buf_set_option(buf, "tagfunc", "v:lua.vim.lsp.tagfunc") -- Ctrl+] for go to definition using LSP instead of ctags vim.api.nvim_buf_set_option(buf, "formatexpr", "v:lua.vim.lsp.formatexpr()") -- Code formatting (gq etc) using LSP Everything else one always sees with Neovim and LSP are other plugins like nvim-cmp or Telescope.
- jeremija 4y ago
  I've been using ALE for years and even contributed to it: https://github.com/dense-analysis/ale https://github.com/dense-analysis/ale

vladvasiliu 4y ago

> I could never change to a non-Vi editor since. This isn't only good, though. Like you, when I don't use vim itself (or nvim nowadays) I use vim bindings in my IDE. But since I do most of my typing in this environment, I've lost track of the number of times I've closed windows by mistake because I have ^w in muscle memory...