Next time, try enabling display of whitespace characters through set list. If I remember correctly, they can help distinguish between the Windows carriage return character and Linux end of line character.

This may help for a quick overview.

LSP maybe portable with it's config if the LSP themselves are independent. Checkout Mason which seems to make it easier to bundle neovim and "portable" LSP. There was another project similar to Mason with some more features, but I forgot it's name. So search around to see if that fits your requirements.

Try using :verbose nmap gc to find out what the shortcut is currently mapped to.

I don't use mini.comment, but I assume it needs an operator after gc to for commenting. I have seen gcc used to comment out the line. Just wanted to make sure you are using the correct mapping.

I think it has to do with the way the Haskell packages are disturbed. So if you installed the pandoc from extra repository, and there was an update for any of the Haskell packages that pandoc depended on, then pandoc will have to be updated again. Meaning, instead of pandoc forcing Haskell updates, it is the other way around.

If you only use pandoc and don't normally program in Haskell, check out pandoc-bin. This way you will only get updates for pandoc itself and its dependencies won't force an update.

For me, it works as well on nightly without any modifications as it did when the archival announcement was made. But I only use formatters and one or two linters. So can't confirm for other features.

That said, I am thinking about changing to conform.nivm for formatting.

The notice on packer suggested to use either lazy or pckr

NOTICE:

This repository is currently unmaintained. For the time being (as of August, 2023), it is recommended to use one of the following plugin managers instead:

lazy.nvim: Most stable and maintained plugin manager for Nvim.

pckr.nvim: Spiritual successor of packer.nvim. Functional but not as stable as lazy.nvim.

Considering null-ls still works on nightly, it should be fine.

I used to get these random freezes where mouse movements are still possible, but everything else seems to freeze. Haven't got any recently and it occured very rarely.

However, if I switch to another tty, using ctr + alt + f key and then switch back to the original tty, it seems to fix itself. It might not be related, but worth trying it out.

Thanks, but that didn't make any difference for me as well. I will let you know if I find anything else.

I guess that's one way to fix it. Thanks for letting me know.

However, I think I will keep searching for a different fix. Playing a sound constantly will keep on nagging me, even though it shouldn't. Also I am worried about what will happen when an application like mpv wants full access to the device, but there is an ongoing stream there.

On a side note, since this came up and I have been paying attention, I noticed that some of the system notification sound that I keep missing are caused due to this delay :(

On the plus side, since I almost constantly listen to some music at low volume, I might actually be doing your fix in a round about manual way. This was how I noticed that system notification played fine, if music was already playing, but not otherwise.

Initially, I used HDMI -> Soundbar -> Monitor. The soundbar handles the sound and forwards the video signal to the monitor. Right now, it's the same, except it is using display port for Laptop to Soundbar connection. Hope I understood the question correctly. If you ever figure out the delay, please do update with a solution.

Sorry, I missed the previous message. Glad you got it working with the help of @rewire@programming.dev.

Regarding the massive list, yeah that is expected. If you haven't got fd or rg installed in you system, telescope falls back to regular find. Find doesn't have any sort of builtin ignore list, so it just lists all the files. If you are using the builtin.find_files normally, I think it executes (at least something close to)

find -not -path "*/.*" -type f

With the hidden=true, it does something along the lines of

find . -type f

Both of these commands are executed from the cwd (normally the directory you started nvim in). If you want it only show to a certain depth, you can use the telescope's setup to change the default find_command

telescope.setup({
  pickers = {
    find_files = {
      find_command = { "find", "-maxdepth", "3", ".", "-type", "f"},
    },
  },
}

Modify that to your requirement and then use the keymap to call builtin.find_files() and it should work.