vim-rooter
project.nvim
Our great sponsors
vim-rooter | project.nvim | |
---|---|---|
24 | 28 | |
1,185 | 1,182 | |
- | - | |
3.6 | 0.0 | |
7 months ago | 21 days ago | |
Vim Script | Lua | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
vim-rooter
-
You don't need 'vim-rooter' (usually) or How to set up smart autochange of current directory
The airblade/vim-rooter plugin is an essential part of my Neovim workflow. It automatically changes current directory (:h current-directory) for every buffer to a more natural one (like to path of its Git repository). For me this has the following benefits:
-
NvimTree - how to get this behaviour?
I use a specific plugin for that, you just have to install it https://github.com/airblade/vim-rooter
-
How to properly cd, so plugins pick up project root?
I just use rooter and avoid thinking about it...
-
How to automatically cd to the git root of the current buffer?
There's vim-rooter, which is great.
- Whenever I'm looking for plugins these days [OC]
-
What’s the best start up screen written in Lua?
No, it doesn't change current directory. For that, use sessions or airblade/vim-rooter (or wait around couple of months for planned 'mini.root' :) ). And, of course, you can create custom items which will change current directory.
-
what are the most underrated plugins in your view?
vim-rooter/project.nvim: changes the working directory to the project root when you open a file or directory.
-
NeoRoot.lua: Change working directory like Monkey🐒
Cool plugin! Can you discuss how this differs from/improves upon vim-rooter and others?
-
NvimTree setting cwd to where current file was opened
I think you need rooter https://github.com/airblade/vim-rooter
project.nvim
-
Is there a way of setting a global variable when switching the project?
Hello, I am using https://github.com/ahmedkhalf/project.nvim for managing projects, and I would like to change a global variable's value depending on the project I switched to. Something like an event when switching, and also the an api with the current project information. I don't find anything
If someone is interested on this, there is an issue for a feature: https://github.com/ahmedkhalf/project.nvim/issues/73
-
Telescope: how to search project directory?
You can use one of the "rooter" plugins like this one to dynamically change your working directory: https://github.com/ahmedkhalf/project.nvim
-
R code chunks not showing using Nvim-R for R Markdown
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.
-
How to manage projects efficiently in neovim using telescope
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
-
Noob question about projects
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
-
olddirs.nvim: oldfiles, but for directories
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.
-
Switching between projects
There I also this one: https://github.com/ahmedkhalf/project.nvim
-
Could use some advice for managing projects in a way that fits my mental model and codebase. Monolithic codebase with project files spread around different working directories. Or just help me change my mental model.
Here's my suggestion: 1. Change current working directory to your logical folder, so you can open file/buffers within logical folder. 2. Use different tabs for different logical folders. Because you can set different tab-local working directories. Or use plugin that automatically change working directory to the logical folder the file belongs to. project.nvim does this well. 3. If you want to open or search monolithic folder, then find file with git files or search using git root as current working folder.
What are some alternatives?
neovim-session-manager - A simple wrapper around :mksession.
telescope-project.nvim
vim-startify - :link: The fancy start screen for Vim.
nvim-bqf - Better quickfix window in Neovim, polish old quickfix window.
nvim-spectre - Find the enemy and replace them with dark power.
mini.nvim - Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
projectile - Project Interaction Library for Emacs
replacer.nvim - A powerful refactoring tool for nvim.
vim-grepper - :space_invader: Helps you win at grep.
telescope-frecency.nvim - A telescope.nvim extension that offers intelligent prioritization when selecting files from your editing history.