lualine.nvim/lua/lualine
shadmansaleh 70691ae350 enhance: undeprecate nvim_lsp and completely remove `nvim` diagnostics source 😉
- Now `nvim_lsp` source shows diagnostics generated by vim.lsp only
  avoids uses vim.diagnostic to avoid deprecation warning on nvim 0.6+
  Why? `vim.lsp.diagnostic` deprecation warnings are way too aggressive.
  And I'm annoyed by people complaining here even though the warning is
  generated by some other plugin (After introduction of nvim_diagnostic
  source lualine just can't produce that warning it used to switch users
  to nvim_diagnostic source with a warning on nvim0.6+).
  Forget it just let anyone that wants lsp specific diagnostics have
  `nvim_lsp` . I'd still recommend using `nvim_diagnostic` over
  `nvim_lsp` as diagnostics generayed by plugins like `null-ls` won't
  showup in `nvim_lsp`
- Remove remanents of `nvim` diagnostics source.
2022-01-12 22:35:44 +06:00
..
components enhance: undeprecate nvim_lsp and completely remove `nvim` diagnostics source 😉 2022-01-12 22:35:44 +06:00
extensions chore: Use paranthesis for function calls. No paran can trip new lua users 2022-01-02 17:38:39 +06:00
themes chore: Use paranthesis for function calls. No paran can trip new lua users 2022-01-02 17:38:39 +06:00
utils chore: remove older deprecation notices 2022-01-12 22:35:17 +06:00
component.lua chore: Use paranthesis for function calls. No paran can trip new lua users 2022-01-02 17:38:39 +06:00
config.lua chore: Use paranthesis for function calls. No paran can trip new lua users 2022-01-02 17:38:39 +06:00
highlight.lua chore: Use paranthesis for function calls. No paran can trip new lua users 2022-01-02 17:38:39 +06:00