hello @shouyierban :)
Can you share your config, I'm not able to replicate the above with my testing.

You may need to run :CyberdreamBuildCache with cache disabled to get the desired result.

thank you for your reply, here is my config:

return {
    "scottmckendry/cyberdream.nvim",
    -- dev = true,
    lazy = false,
    priority = 1000,
    config = function()
      require("cyberdream").setup({
          transparent = true,
          italic_comments = true,
          hide_fillchars = true,
          terminal_colors = false,
          cache = true,
          borderless_telescope = false,
      })
  end,
}

it works only I set cache = false, but there was spend more time to start lazyvim

Can you try setting cache = false so the correct highlights are shown? Once the highlights are showing correctly, run :CyberdreamBuildCache.

This should fix the problem 🙂

Can you try setting cache = false so the correct highlights are shown? Once the highlights are showing correctly, run :CyberdreamBuildCache.

This should fix the problem 🙂

I have tryed in this way, but still no work.
In lieu of that, after I manually modified the cache file and added the following, it displays properly.

{
  "TelescopeBorder": {
      "bg": "NONE"
  },
  "NeoTreeNormal": {
      "bg": "NONE"
  },
  "NeoTreeNormalNC": {
      "bg": "NONE"
  },
  "NeoTreeFileName": {
      "fg": "#ffffff"
  },
  "WhichKeyBorder": {
      "bg": "NONE"
  },
  "WhichKeyNormal": {
      "bg": "NONE"
  },
}

Is there any way to make telescope completely transparent? When I'm not using any colourscheme and it defaults to my terminal scheme, telescope is transparent, but when using cyberdream and the config above, as well as setting telescope options like set_hl, it still isnt transparent.

@Yeastiest try borderless_telescope = false in your config. Probably not the best setting name looking back 😀

@scottmckendry Alright thanks, besides that though I just wanna check, is having transparent telescope, nvim, neotree and all the others at the same time actually possible? Because that’s my end goal.

Setting Telescope to bordered does work! Thanks a lot for the quick help

Hey @shouyierban, can you let me know if the latest commit on main resolves the original issue you reported? The cache option should now handle changes to the config after exiting Neovim the second time.

Hey @shouyierban, can you let me know if the latest commit on main resolves the original issue you reported? The cache option should now handle changes to the config after exiting Neovim the second time.

Hi @scottmckendry , I have updated today. Unfortunately, it dose still not work like before, and I have checked cache file, some configuration iterms still needs to be added manually.

"NeoTreeNormal": {
      "bg": "NONE"
  },
  "NeoTreeNormalNC": {
      "bg": "NONE"
  },
  "NeoTreeFileName": {
      "fg": "#ffffff"
  },
  "WhichKeyBorder": {
      "bg": "NONE"
  },
  "WhichKeyNormal": {
      "bg": "NONE"
  }, 
  "TelescopeNormal": {
      "bg": "NONE"
  }

Is it possible you're loading another colorscheme before cyberdream? The background colour #1e2131 in your screenshot isn't defined anywhere in the code base, so it must be getting set by another plugin somehow.

It has highlighted that both the whichkey and telescope extensions were missing some defaults, so those have been added now.

I don't have an extension for neotree in cyberdream yet, but will look to add support soon. In the meantime, I'd recommend reviewing your config for any other plugins that could be setting these highlights 🙂

Is it possible you're loading another colorscheme before cyberdream? The background colour #1e2131 in your screenshot isn't defined anywhere in the code base, so it must be getting set by another plugin somehow.

It has highlighted that both the whichkey and telescope extensions were missing some defaults, so those have been added now.

I don't have an extension for neotree in cyberdream yet, but will look to add support soon. In the meantime, I'd recommend reviewing your config for any other plugins that could be setting these highlights 🙂

Hi @scottmckendry , good news, it works now! thank you for your nice job, and Looking forward to neotree joining，there will be a perfect theme.
By the way, is it possible to make the autocomplete window of blinkcmp to transparent? the documentation window is transparent now. I'm not sure if this is a theme issue or a plugin issue of blink-cmp.

Great! glad to hear. And thank you for the kind words!

is it possible to make the autocomplete window of blinkcmp to transparent?

Hmm, I don't have an answer to that one. blink.cmp is working fine in my case:

Can you tell me what the output of :hi BlinkCmpMenu is? It should link to Pmenu which, in turn, should have a transparent background. Unless you have that group overridden somewhere else?

You could also try overriding BlinkCmpMenu in your config, like you did for the other groups to see if that makes any difference.

Btw I saw your issue in blink.cmp - I don't think this is an issue with the plugin itself. I'm one of the contributors on that project and have been using it with cyberdream for ages with no problem.

Actually, I can replicate this if I set winblend = 1 in blink.cmp's setup:

removing the winblend option entirely fixes this for me - maybe that is the problem?