this post was submitted on 24 May 2024
14 points (81.8% liked)

Neovim

2102 readers
6 users here now

founded 1 year ago
MODERATORS
 

Update: Based on the discussion here and in other places I added the following (well, technically I did something different in my colorscheme, but in the end it translates to that)

vim.api.nvim_set_hl(0, 'Normal', {})

This reverts the weird text and background colors to the previous behavior of ... not setting them.


With update 0.10 Neovim behavior changed regarding text color and background color.

I use a color theme that does not set those and previously this worked perfectly fine. Neovim simply used the font color defined in the terminal and had a transparent background.

Now the background is #14161b and the font color is #e0e2ea. Neither of the colors is configured ANYWHERE in my whole setup. Neither in the colorscheme, nor in my terminal configuration, nor in my Neovim configuration.

Is there a sane way to revert this to the old behavior? (i.e. use the font color configured in the terminal’s configuration and use transparent background.)

you are viewing a single comment's thread
view the rest of the comments
[–] Dirk@lemmy.ml 1 points 3 months ago (1 children)

vim.opt.background = false

Unfortunately no.

E5113: Error while calling lua chunk: vim/_options.lua:0: Invalid option type 'b
oolean' for 'background', should be string 

When setting to any string (a literal 'false', a hex color string with or without #, etc.) it prints

E5113: Error while calling lua chunk: vim/_options.lua:0: E474: Invalid argument 

vim.opt.guicfg = { background = “transparent”, foreground = “#<idiots_color_hex>”, }

Also no.

E5113: Error while calling lua chunk: vim/_options.lua:0: Invalid option (not found): 'guicfg'
[–] LeroyJenkins@lemmy.world 1 points 3 months ago

oops thought we were talking about emacs this whole time. sorry ignore me and forget this ever happened.