CosmicNvim VS dressing.nvim

Hover/Signature with borders https://github.com/mattleong/CosmicNvim/blob/main/lua/cosmic/lsp/init.lua

Hi everyone! I’m happy to announce that CosmicNvim now includes first-class support for 4 additional themes on top of the default for a total of 5 themes to choose from! The current selection: - [Catppuccino](https://github.com/Pocco81/Catppuccino.nvim) - [Gruvbox](https://github.com/ellisonleao/gruvbox.nvim) - [Rose-pine](https://github.com/rose-pine/neovim) - [Nord](https://github.com/shaunsingh/nord.nvim) - [Tokyonight](https://github.com/folke/tokyonight.nvim) Repo: https://github.com/mattleong/CosmicNvim (⭐️’s are very appreciated!) I’ve previously said that I wouldn’t implement first class theme support for CosmicNvim outside of the default theme… Well, I guess I changed my mind. 😅 For one, it’s probably been the most requested feature. For another, I want to be able to swap and play around with themes easily as well. My initial reason for _not_ wanting to include additional theme support was because I was worried about what sort of complexity it would bring. Turns out it’s not so bad and doesn’t overly bloat the codebase. If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open [issue](https://github.com/mattleong/CosmicNvim/issues/25)!

If you have any suggestions for themes you’d like to see implemented, please feel free to drop them in the open issue!

I'm currently using CosmicNvim along with Bufferline. I have bufferline configured to run `:bdelete! %d` as the close command, but event calling `:bdelete` directly has the same result: neovim is closed completely rather than just the current buffer.

You can check out my config here: https://github.com/mattleong/CosmicNvim

But I didn't do enough research on Cosmic. Installation seemed simple enough. Just git clone. So I backed up my nvim folder and installed it. Carelessly went through the installer. Decided it also wasn't for me. Rather than try to uninstall it, I renamed the folder 'nvim_cosmic' just in case, reverted back to my previous nvim folder, and there's tons of lua related errors.

And currently testing out Cosmic. Just made a backup of my nvim folder first.

Take a look at CosmicNvim! (Disclaimer: I’m the author)

Can’t think of any reasons why Cosmic wouldn’t work on WSL. Haven’t tested it though.

Frequency Sorting for vim.ui.select: Now you can enjoy (f)recency-based sorting for pickers started through vim.ui.select, provided by dressing.nvim or (untested) telescope-ui-select.nvim. For this to work, make sure to load telescope-all-recent.nvim AFTER dressing.nvim.

For 2, I use dressing.nvim with the options below (requires telescope) and that gives me a nice UI for code actions which you can exist out of. lua { input = { enabled = false }, select = { telescope = require("telescope.themes").get_cursor() }, }

cool, thanks, solved my problem, just checked the codebase again with the vim.ui.select, found the plugin stevearc/dressing.nvim

Dressing works, but most of its code deals with vim.ui.select, which seems slightly overkill here.

In general, vim.ui.input does not seem to be super completion friendly, it seems the only method currently available is to use dressing, cmp, and cmp_omnifunc to get some basic completions that are provided by omnifunc: https://github.com/stevearc/dressing.nvim/issues/55

Are you using https://github.com/stevearc/dressing.nvim by chance??? It's awesome to see ui plugins emerging that can be used in other plugins :)

I wrote this little guy which promots you for your query with vim.ui.input, which is really neat if you have a plugin like dressing.nvim installed

it uses vim.ui.select so you can use for example dressing.nvim to use telescope for the UI.

I wanted to share a little utility function, I believe is quite useful. It takes a command as input and shows the output in a scratch buffer. Inputting “scratch” will open an empty scratch buffer, command completions are enabled. It is based on the builtin vim.ui.input prompt, which can be automatically styled by the excellent dressing.nvim. I often use it to open the current colorscheme’s highlight groups in a buffer, with the advantage that colorizer plugins will work then. Or you can check out the latest messages when you got errors in your config, etc. Just don’t try to update your operating system through it…

the little bit of indirection with save_file is required because vim.ui.input might be async (for example if want you're able to use stevearc/dressing.nvim with this snippet without out any modification)