monokai-pro.nvim
vim-projectionist
| monokai-pro.nvim | vim-projectionist | |
|---|---|---|
| 12 | 25 | |
| 377 | 1,033 | |
| - | - | |
| 8.7 | 4.6 | |
| 25 days ago | about 2 months ago | |
| Lua | Vim Script | |
| 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.
monokai-pro.nvim
-
Monokai-pro (but with Tokyo Night palette)
People frequently inquire about lightening the background or adjusting the darkness of specific highlight groups. To facilitate customization, I've provided the option for users to tailor their own color palette. Check it out here monokai-pro.nvim
-
Vim users will do everything they can to have VSCode without actually having to download VSCode
The username appears to be incorrect https://github.com/loctvl842/monokai-pro.nvim https://github.com/loctvl842/nvim
-
Is this Neovim?
Yes : https://github.com/loctvl842/monokai-pro.nvim
- neo-tree colorschemes
-
How to change bufferline background color of file icons?
You can refer to the code from monokai-pro.nvim
-
Color schemes with semantic highlights
monokai-pro.nvim
-
What's the coolest thing you've done with Neovim?
Make my first plugin Monokai Pro
-
What's your neovim colorscheme in 2023 ??
I use Monokai Pro
-
Monokai Pro
Hi, I just applied Monokai Pro, and I love it. But, I can't find proper colorsheme for iterm2. I've found this ayatmaulana/iterm2-monokai-pro, but it's not the same colour (checkout screenshot below)
-
why is my grubox not working as it should? is it a font issue? any help is appreciated
Try this https://github.com/loctvl842/monokai-pro.nvim
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?
tokyonight.nvim - 🏙 A clean, dark Neovim theme written in Lua, with support for lsp, treesitter and lots of plugins. Includes additional themes for Kitty, Alacritty, iTerm and Fish.
jumpwire.nvim - Jump easily between related files.
iterm2-monokai-pro - 🌈 iTerm2 Monokai Pro Color Scheme
denite.nvim - :dragon: Dark powered asynchronous unite all interfaces for Neovim/Vim8
nord.nvim - An arctic, north-bluish clean and elegant Neovim theme.
autojump - A cd command that learns - easily navigate directories from the command line
nvim-config - My neovim config heavily inspired by https://github.com/LunarVim/Neovim-from-scratch
vim-rails - rails.vim: Ruby on Rails power tools
material.nvim - :trident: Material colorscheme for NeoVim written in Lua with built-in support for native LSP, TreeSitter and many more plugins
bufexplorer - BufExplorer Plugin for Vim
tree-sitter-jakt - Tree-sitter for the Jakt Programming Language
fzf.vim - fzf :heart: vim