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, but in the end it translates to that)

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

In the command-line window the command line can be edited just like editing text in any window. It is a special kind of window, because you cannot leave it in a normal way.

There are two ways to open the command-line window:

1. From Command-line mode, use the key specified with the 'cedit' option (default CTRL-F).

2. From Normal mode, use the "q:", "q/" or "q?" command.

• This starts editing an Ex command-line ("q:") or search string ("q/" or "q?"). Note that this is not possible while recording is in progress (the "q" stops recording then).

When the window opens it is filled with the command-line history. The last line contains the command as typed so far. The left column will show a character that indicates the type of command-line being edited

It's been several months since my initial symbols-outline.nvim fork decision post on reddit. It's continued to receive updates and fixes, and yesterday I've finally released the first, initial version of outline.nvim. The full details of all changes since fork detach, and since initial forking can be found in the changelog.

When im using the edit mode with nvchad, sometimes (especially when i press the space or enter keys) an error apear saying Multiple different client offset_encodings detected, this is not supported yet, any idea why does this happen?

I was looking for a good generalist set of keybindings for my Steam Deck's onboard controls that bound all the letter keys and also the necessary commands to navigate web pages and manipulate files. There isn't any obvious layout to bind all the gamepad buttons, joysticks and touchpads to letter keys and keyboard commands/command chords, and further it feels like whatever solution you came up with would be impossible to memorize anyways.

Kind of a silly endeavor perhaps, but... touchscreen keyboards take up wayyyyy too much screen real estate on the Steam Deck, and further the pop up software keyboard sometimes doesn't behave right with software that isn't expecting a pop up touchscreen keyboard (i.e., not like a mobile app designed to handle one).

Then I randomly thought about Qutebrowser and vim keybindings... and I had an evil idea.....

I want to try using this with neovim as well, and I thought y'all might get a kick out of it lol!

edit errr, oooff I don't know how to get lemmy not to dump the text from my linked post completely unformated into this post

Siddharta Govindaraj writes:

As I blogged about in the previous two articles, I recently updated my NeoVim configuration for the fourth time. Although it might sound like a lot of config updates, keep in mind that it happened over a period of four years.

• The first version was a port of my existing Vim configuration. Because NeoVim is backward compatible with Vim, you can just move the configuration over and it will work
• In the second version, I migrated my plugin manager to Packer. This config was a mix of old style Vim config and the newer NeoVim style with some plugins migrated to Lua equivalents
• Then I decided to go 100% Lua config and started using Kickstart.nvim and LazyVim.
• This fourth time around I used Kickstart and LazyVim as guides to write my own from scratch.

You can find my NeoVim configuration on Github.

In this article I am going to go through and explain my configuration step-by-step. I have a terrible memory, so this post will also serve as a guide when I inevitably need to look through this file in the future.

Read Configuring NeoVim as a Python IDE (2023)

btw.nvim

Show "I use Neovim (BTW)" when neovim opens. That's all you need.

Why bother with mini.starter, vim-startify, dashboard-nvim, or any of those distractions? I know you, my friend. Forget about all that noise – all you truly need is I use Neovim (BTW). Embrace it proudly, and let your ego shine!

Features

• Instant Ego Boost: Get greeted with "I use neovim (BTW)" on launch.
• I use Neovim (BTW): Show your ego to the world.

im switching to colemak-dh and i need some advice.

im writing this with colemak-dh, beleive me its hard. whats even harder is the hjkl navigation. so should i remap it to neio? you can consider me a long run guy, so your answers can be based on that.

thanks in advance.

Really enjoying nvim-dap-ui lately, but I always have to adjust the sizes of the windows. The docs have left me high and dry so far, but maybe one of you have a good solution for a consistent layout when you first attach to a file?

Looking for a way to migrate from Arduino IDE to get everything in NeoVim, but I get lost in the weeds without a working example or reference. I'm wondering if this is actually practical and more than a novelty for anyone here.

My goal is to automatically close the environment while editing a tex file. There was an issue for vimtex asking for basically what I want to achieve. They achieve it using snippets as mentioned there.

The problem is, I have no idea how to set it up. I've never used snippets in nvim. I have vim-vsnip and cmp-vsnip installed as it was needed for another plugin to work. Is it possible to implement this using those?

It can be noted that in vimtex, an environment can be closed by typing ]] which is a mapping of vimtex-delim-close. I basically want to emulate the behavior in VS Code using LaTeX Workshop. It auto-closes the environment, adds an indented line in the middle, and moves the cursor there.

If anyone has any other ideas about doing this without snippets, that's welcome too.

Hi I've been looking at nyoom.nvim and it alters the UI of telescope (see screenshot) I was just wondering how this is possible? I looked d through the codebase but couldn't find anything other than the setting of colours?

Here is the repo: https://github.com/nyoom-engineering/nyoom.nvim

cross-posted from: https://discuss.online/post/5797974

TJ has a walkthrough of installing NeoVim and his Kickstart.nvim package for people new to NeoVim. He explains what is going on so you can then further customize your NeoVim setup.

I used NeoVim with Kickstart.nvim to get my NeoVim setup initialized. It's great.