Skip to content

feat: add normal nc highlight group #705

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Oct 9, 2021
Merged

Conversation

kyazdani42
Copy link
Member

@kyazdani42 kyazdani42 commented Oct 8, 2021

closes #704

@kyazdani42 kyazdani42 merged commit ef2c3bf into master Oct 9, 2021
@kyazdani42 kyazdani42 deleted the feat/add-normal-nc-hl branch October 9, 2021 08:36
@mortezadadgar
Copy link

mortezadadgar commented Oct 9, 2021

@kyazdani42 I'm getting this background color on the left side of nvim-tree window now; is there any way to sort this out
image

@kyazdani42
Copy link
Member Author

should be fixed in 22e64cc (1.5.13)
If it still appears you can override the NvimTreeSignColumn color group to link to to Normal

@mortezadadgar
Copy link

should be fixed in 22e64cc (1.5.13) If it still appears you can override the NvimTreeSignColumn color group to link to to Normal

Thanks! linked NvimTreeSignColumn

@siduck
Copy link
Contributor

siduck commented Oct 9, 2021

@kyazdani42 how do I disable the dim? I tried using NvimTreeNormalNC's guibg as the same as NvimTreeNormal but didnt work :/

@kyazdani42
Copy link
Member Author

something like hi! NvimTreeNormalNC guibg=hex_code should work normally

@mortezadadgar
Copy link

@siduck76 try this hi link NvimTreeSignColumn NvimTreeNormal

@siduck
Copy link
Contributor

siduck commented Oct 9, 2021

hi link NvimTreeSignColumn NvimTreeNormal

didnt work :c

@kyazdani42
Copy link
Member Author

might be due to an ordering issue, highlights sometimes are being erased. try putting this in your colorscheme file

@gegoune
Copy link
Collaborator

gegoune commented Oct 9, 2021

Is it possible to completely disable this feature? It shows different SignColumn (to Normal) when active. They are the same when inactive.

@siduck
Copy link
Contributor

siduck commented Oct 9, 2021

might be due to an ordering issue, highlights sometimes are being erased. try putting this in your colorscheme file

I tried it , didnt work out :/

stsewd added a commit to stsewd/tokyonight.nvim that referenced this pull request Oct 9, 2021
@smartding
Copy link
Contributor

@siduck76

highlight! link NvimTreeSignColumn Normal works for me.

@siduck
Copy link
Contributor

siduck commented Oct 10, 2021

@smartding didnt work , NvimTreeNormalNC works

siduck referenced this pull request in NvChad/NvChad Oct 10, 2021
@kyazdani42
Copy link
Member Author

kyazdani42 commented Oct 10, 2021

a temporary solution otherwise if you cannot manage to change the colors would be to change the winhl value in the winopts.

require'nvim-tree.view'.View.winopts.winhl =  table.concat({
      'EndOfBuffer:NvimTreeEndOfBuffer',
      'Normal:NvimTreeNormal',
      'CursorLine:NvimTreeCursorLine',
      'VertSplit:NvimTreeVertSplit',
      'StatusLine:NvimTreeStatusLine',
      'StatusLineNC:NvimTreeStatuslineNC',
      'SignColumn:NvimTreeSignColumn', -- just remove this line
      'NormalNC:NvimTreeNormalNC', -- and this line
    }, ',')

EDIT: as its breaking a lot of people config i guess i'll just map those two to normal for the moment @dbarrosop you'll have to bind the normalNC yourself with hi link NvimTreeNormalNC NormalNC

@gegoune
Copy link
Collaborator

gegoune commented Oct 10, 2021

Still seems to be broken with 64c31aa.

  1. Dimming is active (no way to completely disable it?)
  2. When active, signcolumn is of different colour.

@kyazdani42
Copy link
Member Author

how is that possible ? if dimming is active, it'll just show as normal which should not affect the UI. Same for signcolumn.

Could you make an issue with a small config with custom colors to demonstrate the behavior maybe ? I cannot see any of this with my colorscheme

@dbarrosop
Copy link

dbarrosop commented Oct 11, 2021

@kyazdani42 I actually solved by emptying the list:

    require'nvim-tree.view'.View.winopts.winhl = table.concat({})

It works and I don't require to set links or extra configuration. Assuming I don't want specific highlights for this plugin, is there any reason why I wouldn't do that? If that works and there is nothing wrong with it, maybe it could be an option you can pass to setup.

Thanks again for looking into this :)

@kyazdani42
Copy link
Member Author

i'll extend the setup piece by piece, there are more interesting i want to do first (like finishing the new git integration, adding watchers to not rely on nvim events, rewriting the renderer to make it more customizable, making the initialization faster...)
We'll see, these'll come bit by bit 😄

folke pushed a commit to folke/tokyonight.nvim that referenced this pull request Oct 21, 2021
Almo7aya pushed a commit to Almo7aya/nvim-tree.lua that referenced this pull request Oct 11, 2022
riley-martine pushed a commit to riley-martine/tokyonight.nvim that referenced this pull request Dec 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Dim nvim-tree when inactive
6 participants