Sidebar
Neovim
I [posted about this on Reddit a year ago](https://www.reddit.com/r/neovim/comments/12qvlk0/i_got_the_company_i_work_for_to_donate_to_neovim/), and I figured write about it again: > Like most companies, the one I work for will happilly pay for any employee's license to a proprietary IDE without batting an eye. Therefore, I argued that I should be able to spend that budget on a donation to an open source tool that I use daily instead. After a lot of back and forth I finally got them to donate an amount that would correspond to what they would pay for a yearly subscription to a proprietary tool to Neovim. > > Do you use Neovim at work? If so, I urge you to do the same thing! That way the core team can continue to deliver awesome new features to the editor we all love. [Here's a link to where you can donate](https://opencollective.com/neovim/donate). I now got my work to pay a $400 yearly "Neovim subscription" for the second time. To those wondering how I did it, I basically just argued that since employees at my work have an allocated budget for buying proprietary tools, it makes sense if we could spend an equivalent amount on a FOSS alternative. That way the money spent would benefit us all, and since we use the tool to make money we have a responsibility to give back to the FOSS project. There was a bit of a back-and forth for technical reasons because (at least in Sweden where I live), payments and donations are handled and regulated differently, but they finally made it work. If you also use Neovim for work, I encourage you to do the same thing! That way the core team can continue to deliver awesome new features to the editor we all love. [Here's a link to where you can donate](https://opencollective.com/neovim/donate). There's also the official merch store if you would like to support the project that way: https://store.neovim.io/.
I start my coding workspaces in tmux sessions which persist when I log out. If I switch from a wayland session to an x11 session, then my copy and paste functionality in those neovim sessions are broken because it's still trying to use `wl-copy`. To be more precise: 1. Start a wayland session. 2. Open a terminal and start a tmux session. 3. Open neovim and do some work. 4. Log out of wayland, log into an X11 environment 5. Open a terminal and reconnect to the tmux session 6. `"+y` broken. `clipboard: error invoking wl-copy: Failed to connect to a Wayland server...` Restarting neovim isn't sufficient. I have to restart the entire tmux session or switch back to wayland. Is there some short cut I can take here?
Hi! I've created [refjump.nvim](https://github.com/mawkler/refjump.nvim) which is a plugin that lets you use `]r`/`[r` to jump to the next/previous LSP reference in the current buffer for the item under the cursor. The plugin also automatically integrates with [demicolon.nvim](https://github.com/mawkler/demicolon.nvim) if you have it installed, which I [recently posted about](https://lemmy.ml/post/18974051). This means that you can also repeat the jumps forward/backward with `;`/`,`. [Here's a video showing it in action](https://github.com/user-attachments/assets/7109c1bc-1664-46eb-b16a-fa65c4f05f74). Enjoy!
github.com
[demicolon.nvim](https://github.com/mawkler/demicolon.nvim) is a plugin that lets you use `;`/`,` to repeat more jumps than just `t`/`T`/`f`/`F` like diagnostic jumps with `]d`/`[d` and treesitter text-object jumps like `]f`/`[f` to next/previous function. Now you can also easily make your own custom jumps repeatable with `;`/`,`. For example, I've now made [gitsigns.nvim](https://github.com/lewis6991/gitsigns.nvim)'s `]c`/`[c` repeatable out of the box with demicolon.nvim. [Here's the implementation](https://github.com/mawkler/demicolon.nvim/blob/d6b76531ab093de6ed5280f71450dda91de85398/lua/demicolon/integrations/gitsigns.lua#L4-L16) if you're curious. For more information see [the custom jumps section in the README](https://github.com/mawkler/demicolon.nvim?tab=readme-ov-file#custom-jumps).
When using [LuaSnip](https://github.com/L3MON4D3/LuaSnip) together with [nvim-cmp](https://github.com/hrsh7th/nvim-cmp) and a snippet library like [friendly-snippets](https://github.com/rafamadriz/friendly-snippets) or [luasnip-snippets](https://github.com/mireq/luasnip-snippets) you get a lot of duplicated snippets. That's because the language server also servers snippets. Also, you might want to create your own custom snippet that happens to share the name of a snippet that already exists. For example, with the setup mention above, let's say that I also have a custom `fn` snippet for Rust files. When I type `fn`, nvim-cmp suggests three snippets: one from rust-analyzer, one from friendly-snippets and my custom one. The solution to overriding friendly-snippets with your custom ones suggested in [this open LuaSnip issue](https://github.com/L3MON4D3/LuaSnip/issues/458) is to create your own fork of friendly-snippets. However, this is not ideal because it adds a lot of extra work to each user to ensure that their fork is up-to-date with upstream. Also, it doesn't solve the issue with language servers serving snippets with the same name. I know that for most language servers you can disable snippets, but that doesn't really solve the issue either because you might want some of those snippets. What I would like is the option to only see one of the snippets listed if there are multiple ones with the same name. Which one would be controlled with a priority list, for example: 1. If there's a custom user snippet, use that 2. Otherwise, if there's an LSP snippet, use that 3. Otherwise, use the one from friendly-snippets Is this possible to achieve today?
Hello, I wanted to share a small keymap I made. It lets you inspect unsaved changes in the current file. It uses diff mode, in a vertical split. To close the diff mode, just press q in the scratch buffer. ```lua vim.keymap.set( 'n', '<M-C-D>', function() local tmpft = vim.bo.filetype vim.cmd.vnew() vim.bo.filetype = tmpft vim.bo.buftype = 'nofile' vim.keymap.set( 'n', 'q', '<cmd>bw<cr>', { noremap = true, silent = true, buffer = true } ) vim.cmd('silent r#|0d_') vim.bo.modifiable = false vim.cmd('diffthis|wincmd p|diffthis') end, { noremap = true } ) ``` edit: I discovered that this functionality is actually documented in the help pages (:h :DiffOrig). It’s basically the same action but bound to a command
github.com
Hi everyone! I've created a new Neovim plugin: [demicolon.nvim](https://github.com/mawkler/demicolon.nvim). It lets you use `;` and `,` keys to not only repeat `t`/`T`/`f`/`F` motions, but also to repeat diagnostic motions like `]w` (jump to next warning) as well as jumps to [nvim-treesitter-textobjects](https://github.com/nvim-treesitter/nvim-treesitter-textobjects?tab=readme-ov-file#text-objects-move) like `]f` (jump to next function). [Video previewing it in action](https://github.com/user-attachments/assets/e847cf39-40bd-49cb-9989-34e921b3393a). That's all. Have a great day!
What issues or frustrations have you encountered in trying to use and set up Neovim in Windows 11? I'm currently writing up my experience with installing, setting up, and using Neovim in Windows and would like to hear from others that have tried the same. What was annoying, difficult, or impossible in your experience?
Is there some intuitive menu mode that is simple to initiate? The packaged setup with dnf on F40 only has the colon help menu enabled. I don't care about mouse Luddites or the remarkableness of people with total recall. I need something like gedit level tools to just work without Planck scale resolution help, or learning career to make a useful hobby tool that is free from stalkerware nonsense like an electron based IDE.
Based on answers to the following question: > Which development environments did you use regularly over the past year, and which do you want to work with over the next year? Please check all that apply. Neovim is the most admired code editor in the 2024 Stacked Overflow Developer Survey Source: https://survey.stackoverflow.co/2024/technology#admired-and-desired-new-collab-tools-desire-admire
It's broader than a Neovim specific mapping, I've changed the system keyboard mapping of `<Caps Lock>` to `<Esc>` and `<F9>` to `<Caps Lock>`. I think mapping `<Caps Lock>` to `<Esc>` isn't uncommon for Neovim users. But I like having `<Caps Lock>` available for non Neovim purposes.
[Difftastic](https://github.com/Wilfred/difftastic) is a diff tool that uses treesitter parsing to compare code AST nodes instead of comparing lines. After following the [instructions for use with git](https://difftastic.wilfred.me.uk/git.html) I'm seeing some very nice diffs when I run `git diff` or run `git show --ext-diff`. I thought it would be nice to get the same output for hunk diffs in the fugitive status window, and in fugitive buffers in general (which use the `git` filetype). But I haven't seen any easy way to do it. Has anyone got a setup like this? I can run a command in neovim like `:Git show --ext-diff` to get difftastic output in a buffer. I'm thinking maybe I can set up fugitive to use the `--ext-diff` flag by default, or set up some aliases. But there is no syntax highlighting for the difftastic outputs since the ANSI color codes that difftastic uses in interactive terminal output don't work in neovim, and the syntax highlighting for the `git` filetype assumes standard diff output which is not compatible with difftastic output. For me losing colors is not a worthwhile trade for the otherwise more readable diff output. My best idea right now is to set up a new filetype called `difftastic`, and write a new treesitter grammar or syntax plugin for it. Then set up some kind of neovim configuration to feed output from difftastic into buffers with the new filetype. There is [an open neovim issue](https://github.com/neovim/neovim/issues/15064) discussing adding syntax-aware diffs directly to neovim, but that doesn't seem to have gone anywhere.
github.com
setting it up like this implements the nvim-web-devicons API, so many plugins that depend on that work with mini.icons too! ``` require('mini.icons').setup() MiniIcons.mock_nvim_web_devicons() ```
github.com
Not mine but this is a great plugin for customising the native LSP inlay hints. Hope some of you also find it helpful. This is related to an earlier post I made, asking if there was a way to move the native LSP hints to the end of a line rather than appearing within the line. Found exactly what I was looking for with this plugin!
streamable.com
My new design direction for neovim is "you just sat down in a homie's spaceship and have no idea what any of the buttons do" -- you can see how I did it here with tabby.nvim: https://github.com/Garoth/Configs/blob/da354cd98241dc7582718a9082226fab99403e4a/nvim/init.vim#L752 I'm an oldschool vim guy, so a lot of my plugin tastes lean towards the ancient. Telescope?? Nah I had that figured out with fzf.vim many years ago, and it's stupid fast. Harpoon? Nah, I have marks, permanent undo and location memory, alternate files, fast search. Plus I love using fzf in my terminal so it all blends together so well. I still use vim-plug, it's pretty much perfect, and have no interest in lazy or whatever the new flavor-of-the-year package manager is Neovide continues to be what I believe is the future of neovim. The performance is best in class, probably theoretically better than even terminals can achieve (since rendering can be done much more selectively, understanding vim concepts like floating windows and such, which have compositing in neovide). The idea of "progressive improvements" in a GUI rather than trying to make something totally different is a great call. In the future, they are likely to implement a new age of image rendering too, which would be aware of z-index layering (so you could have a floating window on top of an image -- current image-in-terminal approaches just put the image on top) Airline -- well, this is in the category of "if it aint broke dont fix" -- Airline has been in development for like 11 years and has 2700+ commits, 17k+ stars on github. I mean, this is a ridiculous history, that's more work than most projects on github, just for a statusline. I don't tend to chase trends or replace vim code with lua - who cares - vimscript is stable and reliable Shoutout to the Maple Mono font -- with a lot of amazing ligatures that I didn't have before, super cozy. Demo recorded on an 7 year old samsung chromebook running Wayland/Pipewire Arch with a dualcore cpu, 4gb of ram, 14nm intel integrated graphics, and a 32gb harddrive. Linux is so cool, being able to do that. The ending was... not on purpose lmao
idk im having this issue for a long time. itd be nice to have this fixed. thanks Edit: I that doesnt help: - `term=xterm-...` in shell config - `set-option -ga terminal-overrides ",xterm-256color:Tc"` in tmux config ### solution: thanks to [mazadin](https://lemmy.ml/u/mazadin@lemmy.world) for the solution. im using foo terminal, so setting `set-option -ga terminal-overrides ",foot:Tc"` in tmux.config fixed it. (yeah im dumb)
Been using LunarVim which seems discontinued and started to break recently. Probably moving to SpaceVim soon. Other distro's being used here?
github.com
I made a small plugin that other people might find handy. It checks if the file open in the current buffer has write access and if not, prompts for sudo (or any other command at your choice) and copies the file. No longer do you need to care about forgetting to use sudoedit or anything else, just edit the files you want to edit! This could change the world!!1! But in all seriousness, this is my first neovim plugin and I barely spent an hour on it but it's simple and it gets the job done. It scratches a minor itch and maybe you'll also find it useful.
github.com
This is [parrot.nvim](https://github.com/frankroeder/parrot.nvim), the ultimate [stochastic parrot](https://en.wikipedia.org/wiki/Stochastic_parrot) to support your text editing inside Neovim. Frank Röder started this repository because a perplexity subscription provides $5 of API credits every month for free. Instead of letting them go to waste, he modified his favorite GPT plugin, gp.nvim, to meet his needs - a new Neovim plugin was born! 🔥 Unlike gp.nvim, parrot.nvim prioritizes a seamless out-of-the-box experience by simplifying functionality and focusing solely on text generation, excluding the integration of DALLE and Whisper. ## Features - Persistent conversations as markdown files stored within the Neovim standard path or a user-defined location - Custom hooks for inline text editing with predefined prompts - Support for multiple providers: + [Anthropic API](https://www.anthropic.com/api) + [perplexity.ai API](https://blog.perplexity.ai/blog/introducing-pplx-api) + [OpenAI API](https://platform.openai.com/) + Local and offline serving via [ollama](https://github.com/ollama/ollama) - Custom agent definitions to determine specific prompt and API parameter combinations, similar to [GPTs](https://openai.com/index/introducing-gpts/) - Flexible support for providing API credentials from various sources, such as environment variables, bash commands, and your favorite password manager CLI
I'm normally a straight vim user (just out of habit, no particular preference) and I'm giving neovim a spin. So far I like it but... For the love of all that's holy, how do I disable automatic indentation? I have noautoindent set, nosmartindent set, filetype indent off, but neovim keeps inserting indentations. The only thing that works is setting paste on, but that's not the right solution to this problem. Please help. This is driving me nuts!
I'm on NixOS and slowly working through neovim config. I have treesitter installed with all grammars and it's set up in lua. When I run :TSymbols, it pops open a window showing -----treesitter-----, but no symbols are shown from the (python) code I have open. All of the setup is put in place by the config flake I'm using, but I don't think there's any additional stuff to add for symbols to work. The treesitter section in the resulting init.lua from nix looks like this: ``` require('nvim-treesitter.configs').setup({ ["context_commentstring"] = { ["enable"] = false }, ["highlight"] = { ["enable"] = true }, ["incremental_selection"] = { ["enable"] = false, ["keymaps"] = { ["init_selection"] = "gnn", ["node_decremental"] = "grm", ["node_incremental"] = "grn", ["scope_incremental"] = "grc" } }, ["indent"] = { ["enable"] = false }, ["refactor"] = { ["highlight_current_scope"] = { ["enable"] = false }, ["highlight_definitions"] = { ["clear_on_cursor_move"] = true, ["enable"] = false }, ["navigation"] = { ["enable"] = false, ["keymaps"] = { ["goto_definition"] = "gnd", ["goto_next_usage"] = "<a-*>", ["goto_previous_usage"] = "<a-#>", ["list_definitions"] = "gnD", ["list_definitions_toc"] = "gO" } }, ["smart_rename"] = { ["enable"] = false, ["keymaps"] = { ["smart_rename"] = "grr" } } } }) ```
www.jvt.me
Hi everyone, could someone help a desperate student to turn off the 'Possible spelling mistake found' in LaTeX files with the vimtex plugin. It's been 3h now and I still dont have any idea on how to turn this off (or at least change the language, but knowing how to do both would be really cool). I tried everything I could, still don't kow where this is from. Help would be really appreciated. Thanks in advance.
[kitty-scrollback.nvim v5.0.0](https://github.com/mikesmithgh/kitty-scrollback.nvim/releases/tag/v5.0.0) is officially released! Check out the announcement [here](https://github.com/mikesmithgh/kitty-scrollback.nvim/discussions/259) # What is kitty-scrollback.nvim? A Neovim plugin (and Kitty Kitten) that allows you to navigate your Kitty scrollback buffer to quickly search, copy, and execute commands in Neovim.  Check out the [README](https://github.com/mikesmithgh/kitty-scrollback.nvim) for detailed information, the [Wiki](https://github.com/mikesmithgh/kitty-scrollback.nvim/wiki) for additional configurations, and [Advanced Configuration Examples](https://github.com/mikesmithgh/kitty-scrollback.nvim/wiki/Advanced-Configuration-Examples) for more demos! # What changed? See [Migrating to v5.0.0](https://github.com/mikesmithgh/kitty-scrollback.nvim#-migrating-to-v500) for the detailed migration guide. - kitty-scrollback.nvim v5.0.0 uses Kitty's builtin `--bracketed-paste` option when sending commands to Kitty. The `--bracketed-paste` option was added in Kitty 0.32.2. If you are using an older version of Kitty, then upgrade to the latest version or at least 0.32.2. - Alternatively, if you are unable to upgrade Kitty, then you can still use tag [v4.3.6](https://github.com/mikesmithgh/kitty-scrollback.nvim/releases/tag/v4.3.6) of kitty-scrollback.nvim. - See [kitten-send-text](https://sw.kovidgoyal.net/kitty/remote-control/#kitten-send-text) for more information on the `--bracketed-paste` option. # Other minor version updates - Added experimental tmux support in v4.0.3! See [tmux (🧪 experimental )](https://github.com/mikesmithgh/kitty-scrollback.nvim?tab=readme-ov-file#tmux--experimental-) for setup instructions. - A handful of bug fixes and smaller features, see the [CHANGELOG](https://github.com/mikesmithgh/kitty-scrollback.nvim/blob/main/CHANGELOG.md) for more information. # What's next? The next feature I plan to work on is adding command-line editing support (see [#253](https://github.com/mikesmithgh/kitty-scrollback.nvim/issues/253)). I also plan to complete the work necessary to move tmux support from experimental to stable. If you have any questions, comments, or feedback feel free to create an [issue](https://github.com/mikesmithgh/kitty-scrollback.nvim/issues) or open a [discussion](https://github.com/mikesmithgh/kitty-scrollback.nvim/discussions).
Personal simple statusbar script. https://gitlab.com/-/snippets/3715695 Works best with [Humanoid colors](https://gitlab.com/humanoid-colors/vim-humanoid-colorscheme).
github.com
Hey everyone, I wanted to use Neovim for writing SystemVerilog, but found that there were very few examples or discussions around how to get common plugins like lspconfig, nvim-lint, and nvim-treesitter working together. After building a configuration that works for me, I thought I would share it as an example for others in the future. You can find it here: https://github.com/thecooldaniel/nvim-config-systemverilog Hope it helps someone and feedback/contribution is very welcome.
The presenter compares some of the functionality to Leap.nvim
***Update***: *Based on the discussion here and in other places I added the following (well, technically I did something different in [my colorscheme](https://git.0x7be.net/dirk/neovim-tango-colors), but in the end it translates to that)* ```lua vim.api.nvim_set_hl(0, 'Normal', {}) ``` *This reverts the weird text and background colors to the previous behavior of ... not setting them.* ________ With update 0.10 Neovim behavior changed regarding text color and background color. I use a color theme that does not set those and previously this worked perfectly fine. Neovim simply used the font color defined in the terminal and had a transparent background. Now the background is `#14161b` and the font color is `#e0e2ea`. Neither of the colors is configured ANYWHERE in my whole setup. Neither in the colorscheme, nor in my terminal configuration, nor in my Neovim configuration. Is there a sane way to revert this to the old behavior? (i.e. use the font color configured in the terminal’s configuration and use transparent background.)
So I've just started using the native LSP inlay hints. I was wondering, does anybody know how to move the inlay hints to the end of the line, instead of in the middle of the line? Matter of preference I suppose, but I find it clutters the line too much.
I am trying to install Astro Vim and after installation, I get prompted with a big block of lua errors. I asked some chatbot for what this might mean and it said that it's probably due to an outdated version of nvim... I got the latest 0.10.0 stable. Does someone know on why this might be happening? I get a very similar error when installing nvchad. Here is the output from nvim once I open it ``` Error detected while processing /home/marty/.config/nvim/init.lua: E5113: Error while calling lua chunk: vim/_init_packages.lua:0: module 'vim.uri' not found: no field package.preload['vim.uri'] no file './vim/uri.lua' no file '/home/runner/work/neovim/neovim/.deps/usr/share/luajit-2.1/vim/uri.lua' no file '/usr/local/share/lua/5.1/vim/uri.lua' no file '/usr/local/share/lua/5.1/vim/uri/init.lua' no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/vim/uri.lua' no file '/home/runner/work/neovim/neovim/.deps/usr/share/lua/5.1/vim/uri/init.lua' no file './vim/uri.so' no file '/usr/local/lib/lua/5.1/vim/uri.so' no file '/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/vim/uri.so' no file '/usr/local/lib/lua/5.1/loadall.so' no file './vim.so' no file '/usr/local/lib/lua/5.1/vim.so' no file '/home/runner/work/neovim/neovim/.deps/usr/lib/lua/5.1/vim.so' no file '/usr/local/lib/lua/5.1/loadall.so' stack traceback: [C]: in function 'require' vim/_init_packages.lua: in function '__index' vim/loader.lua: in function <vim/loader.lua:0> [C]: at 0x5586658aa190 [C]: in function 'require' vim/_init_packages.lua: in function '__index' ...marty/.local/share/nvim/lazy/lazy.nvim/lua/lazy/init.lua:61: in function 'setup' /home/marty/.config/nvim/lua/lazy_setup.lua:1: in main chunk [C]: in function 'require' /home/marty/.config/nvim/init.lua:18: in main chunk E484: Can't open file /usr/local/share/nvim/syntax/syntax.vim ```