picker.nvim: customizable and extensible fuzzy finder
(Plugin)

Hi community. I created a plugin called picker.nvim, which is a fuzzy finder plugin for neovim. There are currently over 15 expansions.

github: https://github.com/wsdjeg/picker.nvim



https://redd.it/1oad915

@r_neovim

LazyVim on NixOS
(Tips and Tricks)

Getting Neovim to work on my config was the most complicated part of switching to NixOS back when I moved 3 years ago.

I would imagine that many people might be going through a similar problem, so I wanted to share a LazyVim flake that I've been working on for a while.

Here is the repo: https://github.com/pfassina/lazyvim-nix

I also tried to differentiate it from a few other implementations I saw out there. The main difference is that it is meant to track closely each LazyVim release.

By default, the flake will source the latest plugin version at the time a new LazyVim version is released. If that is not your thing, you can also override it to use the version in nixpkgs.

I also tried to keep the configuration simple and ergonomic. If you are interested, please give it a try and let me know what you think.

https://redd.it/1oabtjv

@r_neovim

have you seen this color scheme?

https://redd.it/1oadj72

@r_neovim

Broot based Neovim navigation
(Discussion)

Hello all.

I don't have ANY experience designing plugins, and perhaps this endeavor doesn't merit a dedicated plugin, but I wanted to present a new way to navigate your filesystem within neovim that utilizes broot (the goal was to have a consistent experience between broot within neovim and broot outside of neovim)

Broot presents a lot of filesystem navigation functionality built in, albeit with more keybindings and less efficient macros than if you were to use the explorer in snack.nvim (I have neither used telescope, nor oil.nvim, nor fzf-lua to do file navigation, I only have experience using snacks.nvim. I avoided oil.nvim because it doesn't have a treeview which is very useful when assessing your directory structure). Again, the goal was to keep the experience consistent between the terminal and neovim experience so you don't have to learn different sets of commands or create bespoke functions in neovim that don't apply outside of neovim. In fact, using broot, you can exploit its "verb" utilities to inject bash scripts directly within broot, which is incredibly useful functionality.

I tried several "broot.nvim" plugins that I thought would work, including this one by 9999years and this one by skyplam, and I was unable to get either of them to work.

To get it working, I basically set up a key mapping that opens a terminal and runs broot. However, the critical component is nvim-unception which prevents broot running in a neovim terminal from opening a nested neovim session. I am communicating with him on attempting to get some further understanding of its RPC layer but it just magically works as of now. I didn't try flatten.nvim or unnest.nvim from u/BrianHuster (please let me know what advantages unnest offers over unception!).

You do need to set up 3 autocomands and a keymap:

-- Open broot in a terminal
local function open_broot()
  local cmd_string = 'terminal broot' 
  vim.cmd('cd %:h')
  vim.cmd(cmd_string)
  vim.cmd('startinsert')
end
vim.keymap.set('n', '<leader>e', open_broot, { desc = 'test termial' })

-- Automatically enter insert mode in terminal buffers (used primarily for entering broot commands)
vim.api.nvim_create_autocmd("TermOpen", {
  pattern = "*",
  callback = function()
    vim.cmd("startinsert")
  end,
})

-- Remove the terminal buffer from the buffer list when you close it
vim.api.nvim_create_autocmd("BufLeave", {
  callback = function()
    if vim.bo.buftype == "terminal" then
      vim.cmd("bd!") -- close the buffer
    end
  end,
})

-- Close terminal buffers automatically when the job exits, which prevents you from having to manually close them by pressing any key
vim.api.nvim_create_autocmd("TermClose", {
  pattern = "*",
  callback = function()
    -- Only close if you're not already viewing another buffer
    -- (avoids closing if it's in a split you're not focused on)
    if vim.fn.bufname() ~= "" then
      vim.cmd("bd!")
    end
  end,
})

I provide a demonstration here. If anyone is at all interested in integrating broot into their filesystem naviagation workflow, please feel free to contact me and I can try to work/learn on how to make this a plugin. I was a bit relived that I didn't have to do any complex code wrapping around broot using lua, but this workflow has been much nicer than using the default snacks explorer (partly because the snacks explorer search algo seems a bit buggy/weird to me). Thanks for reading!

https://reddit.com/link/1oa8mvu/video/dru8cbonzxvf1/player




https://redd.it/1oa8mvu

@r_neovim

Markdown full editing experience plugin (WIP)
(Plugin)

Hi,

For a while I've been looking for plugins that provides the full editing experience in Markdown files, similar to online Markdown editors that provide lots of features similar to:

Trigger text formatting on/off like bold, italic,* strikethrough, code/code blocks, etc...
* List Management like:
* Auto create next item
* Reorder numbered list on addition and deletion
* Easy indentation
* Creating Table of content with a keymap or simple command.

And other cool features, without having to depend on so many plugins.


I started working on putting all those features into one plugin called markdown-plus

This is still WIP, and to be honest I'm using AI to help me as I have no experience in lua or neovim plugins.

https://github.com/YousefHadder/markdown-plus.nvim

I have yet to add so many features but as of now the following are supported:

* Text formatting in normal/visual modes.
* List management.

More details are in the repo README file, I appreciate feedback and contributions.

https://redd.it/1oa4w2t

@r_neovim

Does ","(repeat jump backward) work for mini.jump?
(Need Help)

I deleted all config and keymaps except mini.jump setup(). and "," not work. when using nvim --noplugin it works.


https://redd.it/1oakywj

@r_neovim

NeoVim build, launch and debug
(Need Help)

Hi, experienced NeoVim users!
I would like to know how NeoVim and CMake interact.
I mean... You can write code in an amazing way but... When it comes to build, launch and debug?
I'm interested expecially in C++ development and CMake build description.
Thanks guys!

https://redd.it/1o4yvip

@r_neovim

nvim-cmp compaltes more then i want

https://redd.it/1o4phd6

@r_neovim

nightgem.nvim - a warm & balanced charcoal color scheme

https://redd.it/1ob2bwl

@r_neovim

how do you manage project specific configs?
(Discussion)

There are times plugins need to have different configs per project because their structure may be different but I may not have the control to change the existing project structure.

For example,

1. A repo may have a linter config in non-standard location.
2. A Java project may have different runtime JDK version that ideally LSP should "figure out" on launch.

I'm currently hard-coding the lookup logic in each plugin by checking my directory and loading different configs, but project-scoped configs are scatted across plugins.

Curious if others have encountered this issue?

Thanks

https://redd.it/1oavdnj

@r_neovim

I am experimenting with a light theme that makes use of background colors to make sure colors look both vibrant and legible, what are your thoughts?

https://redd.it/1oaqdvj

@r_neovim

Overseer.nvim users: upcoming breaking changes
(Plugin)

Hi Reddit, it's been a while. I haven't had time to do much development or even maintenance on my plugins recently, but I did manage to scrape together enough time to do a significant refactor to overseer. The goal was to reduce complexity, make simple things easier, and reduce the ongoing maintenance burden. I'm happy with where it's landed, but I did end up removing several features, including some that I know are relatively popular. What am I asking of you? In order of importance:

* Pin overseer in your package manager to the current stable release (v1.6.0) so you don't get surprised by the breaking release.
* Take a look at the changes in the PR. If I removed your favorite feature or you have any thoughts to share, open a discussion.
* If you feel like it, check out the new branch and kick the tires.

https://github.com/stevearc/overseer.nvim/pull/448

https://redd.it/1objkd6

@r_neovim

[Release] boundary.nvim – Visualize 'use client' boundaries in your React code directly inside Neovim

https://redd.it/1ob9jlx

@r_neovim

I made a plugin for Cedar syntax highlighting

https://redd.it/1oatw3q

@r_neovim

Curated test set for colorschemes?
(Discussion)

Is there some collection of files that are useful for manually testing a colorscheme to see that things look reasonable in a "representative" collection of languages? In particular files that use a lot of syntax that are covered by tree-sitter highlight groups would be very useful.

Given how many colorschemes are around I would assume that some kind of set like this exists, but I haven't found one after some light searching around.

Currently when working on my theme I randomly end up stumbling upon something that seems egregious in some particular language, and it would be nice to see such potential issues earlier.

https://redd.it/1obhkuv

@r_neovim