search

TaDaa / vimade

An eye friendly plugin that fades your inactive buffers and preserves your syntax highlighting!
MIT License
494 stars 9 forks source link

Dims current line when `cursorline` is enabled #62

Closed mrjones2014 closed 3 years ago

mrjones2014 commented 3 years ago

https://user-images.githubusercontent.com/8648891/119986798-4ba27300-bf92-11eb-932d-bf24e81751d6.mov

TaDaa commented 3 years ago

Hi I am unable to reproduce this issue. I would need to know what version of nvim is being used and possibly a minimal vimrc where the issue is occurring. Best guess that I can think of right now is that something caused the winlocal CursorLine fade highlight to persist (either a bug or conflict with another plugin).

mrjones2014 commented 3 years ago

Sorry I stopped using vimade a while ago.

lcrockett commented 3 years ago

Can confirm this bug as well. I've tried reproducing the issue and came to the steps outlined below. I am only experiencing this issue on Ubuntu 20.04. An nearly identical NVIM setup on MacOS Big Sur does not suffer from this bug as it seems.

I'm using (both on Linux and MacOS) NVIM 0.5.0 with LuaJIT 2.1.0-beta3 installed by Homebrew, Python 3.9.5 managed via pyenv, and the latest vimade release.

  1. Open NVIM
  2. Open random file within CWD
  3. Create empty vertical split to the right
  4. Open second file in new vertical split
  5. Experience bug originally mentioned in this issue

It doesn't seem to trigger the bug when not using splits and what's interesting is that the problem disappears when opening and closing a floating window (for instance when calling LspInfo or PackerStatus if you have any of those plugins installed), therefore returning to the second file opened in the split. Simply switching between splits also seems to fix the issue as it seems refocusing on the affected split corrects the issue perhaps.

If you need more information, let me know.

Cheers