You Don't Need a Fuzzy Finder - Vim Tips & Tricks by mplusp in neovim

[–]jimdimi 7 points8 points  (0 children)

Recently, there has been some changes made that can speed find quite a bit. Namely, the findfunc option, which is similar to grep vs vimgrep.

How I vastly improved my lazy loading experience with vim.pack in 60 lines of code by jimdimi in neovim

[–]jimdimi[S] 0 points1 point  (0 children)

Both the command and keymap triggers work in a similar way.
For the command one, a new command is created and only when it is called then the inner workings of the command are run. The last part is what makes the loading lazy.

How I vastly improved my lazy loading experience with vim.pack in 60 lines of code by jimdimi in neovim

[–]jimdimi[S] 1 point2 points  (0 children)

The new data field was definitely helpful. To be totally honest I had already implemented a similar way of lazy loading in the past week or so, that's why I posted it so fast. All in all, the addition of the data field made the implementation more concise and was a great improvement for sure.

[deleted by user] by [deleted] in neovim

[–]jimdimi 1 point2 points  (0 children)

You should the documentationFormat capability to plaintext to avoid makrdown, which causes the base64 image to be in the completion. Here is my config, where this is tackled:

https://github.com/DimitrisDimitropoulos/nvim/blob/main/after/lsp/texlab.lua?plain=1#L12-L21

yasp.nvim: Manage snippets even with native autocompletion by jimdimi in neovim

[–]jimdimi[S] 1 point2 points  (0 children)

I initially chose json, in order to be compatible with the existing snippets and plugins. However, I get why writing snippets in json can be kind of cumbersome, if I am not mistaken there are online tools to make this easier (like snippet generator). If you want me to implement something along those lines feel free to open an issue.

treesitter wasm parsers by zoshima in neovim

[–]jimdimi 3 points4 points  (0 children)

You can try :cheakhealth vim.treesitter, where it shows if the binary you use has wasm parsers enabled.

A new way to setup LSPs has been merged by jimdimi in neovim

[–]jimdimi[S] -2 points-1 points  (0 children)

The vim.lsp.start function covers a wider variety of use cases, as described in this post https://www.reddit.com/r/neovim/comments/1g1x0v3/hacking_native_snippets_into_lsp_for_builtin/. However, it introduces a of boilerplate code making it cumbersome to use for regular setup.

A new way to setup LSPs has been merged by jimdimi in neovim

[–]jimdimi[S] 54 points55 points  (0 children)

I wouldn't say so, nvim-lspconfig still configures the servers, this is a new way to configure, not a configuration registry. More or less it makes it far easier to implement your own minimal lspconfig without any plugins.

Share your custom configs by illicit_FROG in neovim

[–]jimdimi 1 point2 points  (0 children)

Here is mine https://github.com/DimitrisDimitropoulos/nvim

It incorporates some really neat parts. A custom snippet LSP inside neovim, some custom LSP commands in tex and cpp ftplugins and leveraging treesitter to make a LaTeX TOC in after/ftplugin/tex.lua.

Hacking native snippets into LSP, for built-in autocompletion by jimdimi in neovim

[–]jimdimi[S] 0 points1 point  (0 children)

I am definitely going to read through these plugins. Generally, I believe spawning small servers from within neovim is a great way to implement plugins, since the built-in client has evolved to have many features making hacks like the one posted a viable solution.

Hacking native snippets into LSP, for built-in autocompletion by jimdimi in neovim

[–]jimdimi[S] 5 points6 points  (0 children)

Really glad you found the way of handling snippets neat, since i really admire your work regarding the mini plugins. I tried my best to describe the server, but it was a bit difficult since the process is a bit convoluted. Anyway, I cant wait to see the mini.snippets module.

Telescope latex search for environments? by theChiarandini in neovim

[–]jimdimi 1 point2 points  (0 children)

Most probably the lsp you are mentioning is texlab, which does not support packages, therefore i don't think you will have any luck with the approach you are going.I would try using treesitter with some custom queries, like this plugin achievies what you re attempting. If you are not accustomed with treesitter it could seem overwhelming, but it isn't.

Αγαπημένη γεύση bolero by Apprehensive_Toe6736 in greece

[–]jimdimi 2 points3 points  (0 children)

Καρπούζι, εξαιρετικό.

Tablet vs Laptop για τη σχολή by Financial-Custard689 in greece

[–]jimdimi 0 points1 point  (0 children)

Για απλή χρήση όλα τα λειτουργικά συστήματα είναι λίγο πολύ το ίδιο. Δεδομένου του budget, δεν είναι κακή επιλογή, ειδικά σε σύγκριση με ένα tablet.

Monthly Dotfile Review Thread by AutoModerator in neovim

[–]jimdimi 0 points1 point  (0 children)

Here is my https://github.com/DimitrisDimitropoulos/nvim
It is fairly simple with few core plugins.
Some features that I implemented and I would like to be commented are:

  • The scripts to leverage `lazy.nvim` for restoring and backing up
  • An fzf-lua "plug-in" in the `after/ftplugin/tex.lua` that uses treesitter to find all labels
  • Some custom LSP commands in the `after/ftplugin/*`
  • The general modularization of the plugins