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.

That makes sense. Which-key doesn’t allow the timeout to take place after gc since it knows about gcc. While that functionality is useful when you don’t know which key to press next, in situations like these it would create problems. I think your best solution would still be to modify the mappings. Maybe remap gc to gcl (comment last) or something like that.

Like I said, I haven’t used mini.comment, but having both gc and gcc mapping may cause problems. If I remember correctly, in these situations, neovim waits after receiving gc command to figure out if you are trying to execute comment last or gcc with comment line. Depending on timelen (or timeout, forgot the exact name) setting the command you actually execute will defer based on the key pressed/not pressed after gc.

Also, if gc is mapped to comment last, and there was no last comment action performed, it might do nothing (maybe check the readme to be sure). So maybe try changing the mapping to see if that helps.

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.

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.

I have noticed this too on pipewire. Everytime a new audio stream starts , even from a paused state, there is a small delay before it is heard. Not a syncing problem as the audio is synced, but a delayed start. I thought it might have something do with the sound bar I had routed the audio through. Based on your experience, seems not. I did experience the same delay when using HDMI port instead of DisplayPort too (IIRC). So it might be something else not related to port.

There is also this official extension. IIRC, this also makes sure that all the meta owned sites are not able to interact with other sites, but can work fine with each other. It also makes sure that any links leading to their sites also only open in the container, maybe also sanitized to remove the tracker from original link. The last part I am not sure, as I might be confusing it with a different extension. But if you are using any of the Meta sites, I would recommend it.

If you are trying to switch from Chrome, then just use regular Firefox with the ublock extension (and maybe some of the other privacy extension officially supported). If you are a “power user” and want modify/access about:config and other settings then you need Firefox Nightly. The Fennec and Fenix (iirc) are just stripped down Firefox that either only have private mode or additional settings for privacy (that are already present in regular version, but way not be enabled by default). Hope that helps.