project.nvim VS telescope-frecency.nvim

Here is what I have searched: 1. https://github.com/ahmedkhalf/project.nvim/tree/main : plug manage already exist projects, not create 2. https://neovim.io/doc/user/lsp.html : too complicated 3. https://www.youtube.com/watch?v=NL8D8EkphUw&ab_channel=JoseanMartinez : basic tutorial 4. https://www.reddit.com/r/neovim/comments/ysg4wb/lsp_action_on_multiple_files/ : Mentioned use quickfix, but seems too be a workaround. Not a nice solution.

If someone is interested on this, there is an issue for a feature: https://github.com/ahmedkhalf/project.nvim/issues/73

You can use one of the "rooter" plugins like this one to dynamically change your working directory: https://github.com/ahmedkhalf/project.nvim

https://github.com/ahmedkhalf/project.nvim I have never used this but it seems to involve defining "projects", and any time you enter a project, whatever settings you require (such as current working directory) will get set up for you.

Not sure if this is what you are looking for, but projects.nvim automatically changes your pwd in nvim. If you then use telescope's find_files and to search in the pwd, you basically get project-scoped searches. https://github.com/ahmedkhalf/project.nvim

This works very well: https://github.com/ahmedkhalf/project.nvim

Maybe you have ahmedkhalf/project.nvim setup. In this case, use `manual_mode` as indicated in the readme https://github.com/ahmedkhalf/project.nvim. It worked for me

Not sure what you mean by that. Perhaps your looking for a fuzzy finder. I use telescope for most of this. It can be used to find any file in your project and there's extensions for pulling up projects

project.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'm mainly developing a telescope.nvim extension: telescope-frecency.nvim. You should use this if you are searching a cleverer picker to find files in history than :Telescope oldfiles.

I have been working on restructuring telescope-frecency.nvim. One of the biggest changes is removing dependency for sqlite.lua.

I found https://github.com/nvim-telescope/telescope-frecency.nvim but that adds an entirely new picker instead of just sorting the default ones, and I couldn't figure out how to "pipe" the default pickers' lists through it

Is it this plugin?

So how is this different from https://github.com/nvim-telescope/telescope-frecency.nvim?

I wrote my first little plugin - telescope-all-recent.nvim - and wanted to share it. It is inspired by the telescope extension https://github.com/nvim-telescope/telescope-frecency.nvim.

Frecency extension. Frecency is a fancier extension with smart algorithms, and persisting the results to the local database. However, frecency is not recency. This extension is much simpler - the algorithm is as dumb as it can be (whatever opened last is shown last), and there is also no local database to maintain.

Could also try https://github.com/nvim-telescope/telescope-frecency.nvim which gives you some context, with the workspace definitions defined for your projects. Then use something like https://github.com/nvim-telescope/telescope-project.nvim to move between the different projects.