flow.nvim
project-settings.nvim
flow.nvim | project-settings.nvim | |
---|---|---|
8 | 5 | |
105 | 16 | |
- | - | |
7.1 | 0.0 | |
6 days ago | almost 2 years ago | |
Lua | Lua | |
MIT License | MIT License |
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.
flow.nvim
- Help me understand how you use/would use this plugin. Gathering ideas for building a good roadmap
-
July updates to my plugin "run-code.nvim"
Docs for the telescope extension: https://github.com/arjunmahishi/run-code.nvim/wiki/Run-code-launcher
-
Run Python venv from nvim
Thank you everyone for the suggestions. In the end I ended up using a combination of Poetry, Direnv, and the run-code neovim plugin.
-
Made some changes to my "run-code.nvim" plugin
Plugin: https://github.com/arjunmahishi/run-code.nvim
-
What do you prefer for NOTE TAKING or similar purposes?
I used to use Typora before I got into Neovim and realised that it wasn't free software either. Now I'm quite satisfied with my current setup, which uses: - aerial.nvim for header outline and navigation - run-code.nvim for running code blocks - vim-mundo for persistent undo history traversal (like Mac's time machine) - Prettier for auto-formatting Markdown as well as code blocks to their respective languages
- Wrote my first nvim plugin "run-code.nvim" :) It can be used to quickly run snippets of code without leaving the editor. Check it out and let me know what you think
- Wrote my first nvim plugin "rund-code.nvim" :) It can be used to quickly run a snippet of code without leaving the editor. Check it out and let me know what you think
- Wrote my first nvim plugin :) Check it out and let me know what you think
project-settings.nvim
-
I didn't know before that having multiple Neovim instances is bad
That command actually uses project-settings.nvim to setup all the things, not just lsp.
- Run Python venv from nvim
-
Some questions about Lua plugin development
If it helps, you can take a look at this little plugin I made: project-settings.nvim.
-
Using project-settings.nvim to call language servers
project-settings.nvim is a plugin I created to handle some unique scenarios I faced in a couple of projects. It allows you to reuse a lua function across multiple projects, and pass arguments to it using a json file. (I know one could just use an exrc file, but I don't like them).
-
How do y'all feel about handling project local settings using a json file?
Once again I found myself turning a piece of my config into a plugin. This time around it is the project local settings: project-settings.nvim
What are some alternatives?
vim-mundo - :christmas_tree: Vim undo tree visualizer
workspaces.nvim - a simple plugin to manage workspace directories in neovim
vim-run - Run, view, and manage UNIX shell commands with ease.
nvim-config-local - Secure load local config files for neovim
mdeval.nvim - Neovim plugin that evaluates code blocks inside documents
editorconfig-vim - EditorConfig plugin for Vim
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
plugin-template.nvim - A template to create Neovim plugins written in Lua
nvim-cmp - A completion plugin for neovim coded in Lua.
nvim - One editor to roll them all. (GotoDef FindRef Completion Snippet Format Lint Refactor Test Debug Repl Task)
nvim-treesitter-context - Show code context
penvim - Project's root directory and documents Indentation detector with project based config loader