workspaces.nvim VS Comment.nvim

`:tcd` into that project's folder. I'm using workspaces.nvim to create aliases for my project's folders, so I can simply do `:WorkspacesOpen MyProject`

workspaces.nvim.

Sharing a lightweight plugin I wrote yesterday which provides some functions for accessing previously used current working directories. I know that this is similar to some other "workspace" / "project" plugins which already exist, so I've pasted the motivation section from the README. >I work in a large monorepo and change my working directory depending on what part of the codebase I'm looking at to give my LSP (gopls) a chance and to improve the usefulness of fuzzy finding files. I want to change the current working directory back to a previously used one without having to configure a "project" or "workspace" beforehand. This requirement is not satisfied (as far as I can tell) by existing similar plugins: > - project.nvim > - telescope-project.nvim > - workspaces.nvim. > - neovim-session-manager > olddirs.nvim is very lightweight and doesn't provide any niceties (out of the box) like some of the above plugins, it's literally just :oldfiles for directories. > \ I say "out of the box" since some features like the searching or browsing of files inside a previous directory can be implemented by adding actions to the olddirs.nvim Telescope picker.

i use workspaces for that, https://github.com/natecraddock/workspaces.nvim

I use https://github.com/natecraddock/workspaces.nvim and their compatible session manager. I have not tried the other two but workspaces works well and has done nice integrations (including telescope).

I use only one neovim instance and with the plugin https://github.com/natecraddock/workspaces.nvim I change between repositories.

I'm biased, but my favorite is a combination of workspaces.nvim and sessions.nvim (I created both). Both are extremely simple frameworks meant to be customized to your needs. Not for everyone, but if you are looking for something simple its worth giving a look.

workspaces.nvim

Treesitter is a syntax parser that'll build a tree-like structure to enable anything from excellent syntax highlighting through to complex refactoring. There are so many creative ways you can use Treesitter, from jumping around text objects to commenting sections of code, it's a must-have in my books.

A couple nice quality of life plugins would be: Comment (which lets you use a keybinding to comment/uncomment things), Autopairs (which will make the paired brackets/parentheses/etc.), and Rainbow2 (which color-matches the pairs if things like parentheses).

I am reading the documentation for the [Comments](https://github.com/numToStr/Comment.nvim] plugin with :h comment.config and I see this

I was wondering what plugins you use for comments, actually, I'm using numToStr/Comment.

Nowadays, people (mostly) autogenerate their help docs with either markdown or emmmylua are their source. You are facing an issue that I faced before with Comment.nvim.

Comment.nvim?

Based on your reply I recommend taking out the comment plugin, replacing it with https://github.com/nvim-treesitter/nvim-treesitter-textobjects and https://github.com/numToStr/Comment.nvim