project.nvim
vim-projectionist
Our great sponsors
project.nvim | vim-projectionist | |
---|---|---|
28 | 25 | |
1,214 | 1,032 | |
- | - | |
0.0 | 4.6 | |
6 days ago | about 1 month ago | |
Lua | Vim Script | |
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.
project.nvim
-
What is the simple straight answer to create lsp workspace and add files to workspace in neovim ?
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.
-
Is there a way of setting a global variable when switching the project?
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
-
Smart current working directory
This works very well: https://github.com/ahmedkhalf/project.nvim
-
Nvim-tree opens the git root directory instead of the one passed as argument
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
-
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.
vim-projectionist
-
What plugins do you use to manage work across multiple files?
Tim Pope's projectionist for navigating to files of a particular category or to related files from the current one: https://github.com/tpope/vim-projectionist.
-
A few words on Ruby's type annotations state
> For myself, I'm fine with the typing being in a separate .rbs file
We type[0] by having one separate .rbs file per .rb file. Works really well with an editor's vertical splits: type outline on one side, code on the other. That, or use something like vim-projectionist[1].
[0]: (WIP: there's a huge codebase to type, but we're progressively getting there) https://github.com/DataDog/dd-trace-rb/tree/master/sig
[1]: https://github.com/tpope/vim-projectionist
-
What's the coolest thing you've done with Neovim?
One of the originals I guess must be tim pope's https://github.com/tpope/vim-projectionist
- 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.
-
Project & File navigation
use https://github.com/tpope/vim-projectionist - define the relationships between files (example: app/*js are 'source' files and test/*js are 'test' files). Projectionist sets up `:A` to jump to the 'alternate' file (jump between a 'source' file and its 'test' for instance), and `:Esource` and `:Etest` commands to find/navigate by the kind of file. This is very powerful IMO - for projects with good structure I can quickly jump between related test/source/model/blah files very quickly using these commands. For projects without good structure I rethink or get the team to talk about how we might improve the project organization (ie, lack of structure is a code smell!)
-
New Plugin: telescope-alternate
I love Tpope’s https://github.com/tpope/vim-projectionist but this one seems like a great replacement 😎
-
JVM language users- how do you write your test files?
Tim Pope's excellent Projectionist plug-in has an alternate file feature, which makes it very easy to switch between test and implementation files.
-
other.nvim - open alternative files for the current buffer.
The plugin is inspired by vim-projectionist and https://github.com/vim-scripts/a.vim
-
vim-projectionist isn't autoloading in Vim
This feels like a bug, since the plugin doesn't behave as expected when following the installation section verbatim. I filed a bug here: https://github.com/tpope/vim-projectionist/issues/168
-
Auto-open unit test file
You need https://github.com/tpope/vim-projectionist. Gotta have a file structure for unit tests though.
What are some alternatives?
vim-rooter - Changes Vim working directory to project root.
jumpwire.nvim - Jump easily between related files.
neovim-session-manager - A simple wrapper around :mksession.
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
telescope-project.nvim
autojump - A cd command that learns - easily navigate directories from the command line
mini.nvim - Library of 35+ independent Lua modules improving overall Neovim (version 0.7 and higher) experience with minimal effort
vim-rails - rails.vim: Ruby on Rails power tools
lsp-zero.nvim - A starting point to setup some lsp related features in neovim.
bufexplorer - BufExplorer Plugin for Vim
projectile - Project Interaction Library for Emacs
fzf.vim - fzf :heart: vim