zellij-org / zellij

A terminal workspace with batteries included
https://zellij.dev
MIT License
20.25k stars 630 forks source link

Theming affects pane contents #675

Open a-kenji opened 2 years ago

a-kenji commented 2 years ago

The theming of zellij has an effect on pane contents, which is maybe a cool feature? But it isn't obvious to me and I would like an option to turn it off, or it is a bug in that case we could fix it.

Basic information

zellij --version: 0.16.0 tput lines: 30 tput cols: 120 uname -av or ver(Windows):

nvim --version: NVIM v0.5.0 alacritty --version: alacritty 0.9.0

Example config file:

themes:
  edge_dark_def:
    bg: [44, 46, 52]
    fg: [197, 205, 217]
    black: [62, 66, 73]
    red: [236, 114, 121]
    green: [116, 201, 128]
    yellow: [222, 185, 116]
    blue: [108, 182, 235]
    magenta: [211, 138, 234]
    cyan: [44, 46, 52]
    white: [197, 205, 217]
    orange: [232, 128, 44]

Relevant configuration in nvim:

        let g:edge_style = 'default'
        let g:edge_enable_italic = 1
        let g:edge_disable_italic_comment = 1
        let g:airline_theme = 'edge'

        colorscheme edge

Link to the colorscheme.

Inside of zellij with the theme. image Inside of nvim in zellij with the theme. image Outside of zellij in nvim. image zellij.log zellij-9.log

ruihildt commented 1 year ago

Trying neovim for the first time, I have weird visueal artefacts: image image

I didn't customize either theme from bash, neovim or zellij. Everything is just default config from Fedora + KDE.

Is there a way for me to get rid of those visual artefacts?

imsnif commented 1 year ago

Hey @ruihildt - I think the issue you're experiencing is unrelated to the original issue, which is about themes affecting the contents of panes (which I was personally never able to reproduce).

Could you please open a new issue and follow the instructions for reporting a graphical issue that will pop up for you? That will allow us to reproduce the issue and find a solution. Thanks!

ruihildt commented 1 year ago

Hey @imsnif, thanks, reported as issue #2037.