nvim-treesitter-refactor VS kickstart.nvim

Maybe this? nvim-treesitter-refactor

These days though I'm using the https://github.com/nvim-treesitter/nvim-treesitter-refactor plugin. It goes one step further and only highlights the matches that are in the same scope. Makes a big difference in a lot of programming languages where you use the same variable named in a lot of smaller functions/methods right next to each other.

My desires are not sated, but it seems quite nice. (I recall treesitter-refactor has a similar scope highlighter, but it could be a bit aggressive near root scope -- this might be a more gentle version.

check https://github.com/nvim-treesitter/nvim-treesitter-refactor/

Treesitter performance is a hard problem. First, check the following: 1. Do you use nvim_treesitter#foldexpr()? Try not to use foldmethod=expr in insert mode. Or just switch to nvim-ufo. 2. Do you use nvim-treesitter-refactor's highlight_definitions or highlight_current_scope? These features do slower the performance. Try to disable these features. 3. I've heard some language parser is not good in terms of performance. Since I don't write haskell, I can't help you here. But you can create issue in nvim-treesitter.

For instance, with plugins like nvim-treesitter-refactor and ray-x/navigator.lua, you can use a bunch of commands like "go to definition" and "smart rename" without an LSP server.

TS Refactor

get_node_text was removed from ts_utils. create a pull request to fix it, something like this: https://github.com/nvim-treesitter/nvim-treesitter-refactor/pull/33

If you have treesitter, you can use nvim-treesitter-refactor. It has the highlight_definitions option that will highlight the definitions of a variable.

Oh! I've actually never tried Emacs text navigation. My brief stint with Emacs was with Spacemacs (w/ the evil-mode plugin). If I knew any lisp when I had given Spacemacs a whirl then there's a chance I may have stuck with it. I've played with Clojure a bit. Ah, it appears that you're a data-eng -- heavy on the Python. Are you trying to mimic something that PyCharm provides? I'm just happy that LSP has come where it has in such little time and that's already improved working with code in various languages quite a bit. Neovim moves incredibly fast and having LuaJIT with support for Lua had completely opened the floodgates for ports of old Vim plugins and made way for newer ones with floating windows/floating terminals. There are two projects each with hundreds of stars on GitHub meant to mimic or one-up org-mode (one has an entirely new spec) with immense development activity. The one-up that Neovim has over Vim presently is tree-sitter (because the core team wrote a wrapper) and exposes a Lua interface for plugin devs that want to use it. It's been neat for themes and my new favorite find-and-replace plugin (https://github.com/nvim-treesitter/nvim-treesitter-refactor). Because there's type data coming from the AST, it's much less likely to have accidental replacements (if at all). It looks like Emacs is making some headway here, though: https://github.com/emacs-tree-sitter

I recently started coding with Neovim using kickstart.nvim as the template for my editor configuration. I downloaded the python-lsp-server package using Mason, but I was disappointed to discover that the IntelliSense on my third party dependencies didn't work. The LSP was resolving to my global Python installation, which did not have the packages from my virtual environment (venv) installed.

First thing I did was get kickstart.nvim. I had heard it was extremely useful (and it was). It was very easy to install. I start reading through init.lua, and it told me to run :Tutor, which is almost 1,000 lines of learning how to use Neovim, to which I obviously ran that command and started reading. Obviously, it takes a bit of time to complete :Tutor, but it's well worth it. "hjkl" wasn't too hard to get used to, also repeating motions by using numbers was useful, such as using '5dd' to delete 5 lines. I highly suggest reading this file, especially since I didn't really know about the different modes, which is probably why I failed to switch the other times. You would start writing your code, then Neovim would say that it can't find that command, you would accidently type an i and then start typing, and so on, it was a nightmare. For those that don't know the modes, here is each mode and how to get between them.

I also suggest against using distributions. Instead of learning how to configure nvim itself you're learning to configure that specific distro.

I suggest to take someone's lua config and start from there. Kickstart.nvim is a good one: https://github.com/nvim-lua/kickstart.nvim

1) the option I wouldn’t chose, use Kickstarter. It’s a minimal starter config, using a single init.lua that helps you build a config slowly. https://github.com/nvim-lua/kickstart.nvim

I highly recommend Lazyvim for if you want to have a VSCode (ish) like experience that still exposes you to configuring in Lua. Or Kickstart.nvim if you want a more "from scratch" experience

In case it is helpful, I am using kickstart.nvim with only minor modifications.

One of the project goals is to become something like kickstart.nvim. Or, to be a reference if someone doesn't know how to do something.

Hey guys! I don't use the "./" path at all since I see it useless, I would love to remove it to be kind with my own soul, I'd love some help with this. My nvim setup is kickstart.nvim with Lua of course.