impatient.nvim VS trouble.nvim

You could use impatient.nvim or the new vim.loader module if you’re on nightly. Both work really well. I used impatient for a long time and it reduced my startup time by half. I’m using vim.loader now and it reduces it by about the same amount

The 20-30 ms promise depends on your hardware. In my case, vanilla Neovim takes about 18 ms to startup, so a realistic good startup time for my config is around 50-60 ms. Lines of code isn’t a great reference either because you could just lazy load a bunch of plugins and have more LoC but still better startup times. What I would recommend is using lazy.nvim or if you wanna stick with packer, then pairing it with impatient.nvim .

automatically caches all startup code before :h VimEnter or :h BufReadPre (basically what impatient.nvim does)

there is an amazing plugin called impatient.nvim that cache a lot of stuff and make other pluggins go so fast !

Try installing https://github.com/lewis6991/impatient.nvim first.

:lua vim.pretty_print(vim.mpack.decode(vim.mpack.encode({some = { thing = false }}))) used by impatient.nvim

Did you defined your [[ and ]] mappings in that file or just created it? the after directory runs at the end of your config so you can override this kind of settings. Maybe you are using impatient.nvim? From their README:

Are you using impatient.nvim? It caches lua modules. My startuptime with 72 plugins (including it) and zero lazy loading is 600ms.

A newbie here, I used jose-elias-alvarez/null-ls.nivm for diagnostics and formatting, but I recently discovered folke/trouble.nvim and for me, it seems like a better option However, I don't know if it supports formatting and linting, I don't even know if it is an alternative to null-ls. So I need your help, can trouble.nvim replace null-ls? If not, can I use both of them simultaneously?

All you need is just the LSP working (with linter, formatter and diagnostics) and telescope. Seriously, telescope is the GOAT, way faster than a file tree, you end up using the filetree only to move, create and delete files/folders but if it's just for that, you might as well use the terminal instead. For the LSP, it's not only autocompletion and hints at hover but formatting and diagnostics. I use lsp-zero + null-ls + trouble. I exposed all of the keybindings on those so I can at least open my own configs for guidance. Oh yeah, having treesitter is probably a must too, and it has no keybindings on its base form.

I am referring this as well as this this plugin.

Trouble: https://github.com/folke/trouble.nvim

Trouble is so good for finding errors easily. For testing I use jest so I haven't had too many issues. What do you test with?

I like trouble.nvim

I guess LazyVim uses https://github.com/folke/trouble.nvim for it. I should config it to not including errors regarding standardization.

Great feedback, thanks! I’ll certainly have a look into using the LSP to reduce the amount of tests to run. For me, the notifications are a handy feature since our ruby code runs in a docker container. It takes quite some time to attach to the container and run the test file. (This was actually one of the motivations for writing this plugin) However, you can disable notifications and rely completely on the diagnostics. With another plugin like trouble.nvim, you could see the updates in a separate window. Only downside to this, it will be cluttered with other LSP diagnostics. I chose this approach since I am not a fan of creating just another status window, maybe I’ll have to revisit this opinion.

local telescope = require("telescope") local trouble_provider = require("trouble.providers.telescope") telescope.setup({ live_grep = { --@usage don't include the filename in the search results only_sort_text = true, theme = "dropdown", }, extensions = { fzf = { fuzzy = true, -- false will only do exact matching override_generic_sorter = true, -- override the generic sorter override_file_sorter = true, -- override the file sorter case_mode = "smart_case", -- or "ignore_case" or "respect_case" }, }, defaults = { vimgrep_arguments = { 'rg', '--color=never', '--no-heading', '--with-filename', '--line-number', '--column', '--hidden', '--smart-case', '--glob "!.git"', }, mappings = { i = { -- source: https://github.com/folke/trouble.nvim [""] = trouble_provider.open_with_trouble, }, n = { -- source: https://github.com/folke/trouble.nvim [""] = trouble_provider.open_with_trouble, }, }, set_env = { ["COLORTERM"] = "truecolor" }, -- default = nil, }, }) -- source: https://github.com/nvim-telescope/telescope-fzf-native.nvim require("telescope").load_extension("fzf")

With this config I avoid the inline diagnostics, I like pylint, but some errors, warnings and hints aren't useful to me, they are too much noise in my editor, so I use trouble.nvim to watch them when I need to.