Code Monkey home page Code Monkey logo

Comments (4)

nonetallt avatar nonetallt commented on May 20, 2024

Make sure you're using the correct key for your configuration. You're using default_user_settings while the one advertised in readme.md is called user_default_options.

I also had an issue with the names option before I realized I wasn't using the correct keys (in my case I tried to set names at the top level instead of the correct default_user_settings key.

from nvim-colorizer.lua.

B4mbus avatar B4mbus commented on May 20, 2024

@nonetallt I have it set to user_default_options but it still doesnt work:

      colorizer.setup({
        user_default_options = {
          RGB = true, -- #RGB hex codes
          RRGGBB = true, -- #RRGGBB hex codes
          names = false, -- "Name" codes like Blue or blue
          RRGGBBAA = true, -- #RRGGBBAA hex codes
          AARRGGBB = false, -- 0xAARRGGBB hex codes
          rgb_fn = true, -- CSS rgb() and rgba() functions
          hsl_fn = true, -- CSS hsl() and hsla() functions
          css = false, -- Enable all CSS features: rgb_fn, hsl_fn, names, RGB, RRGGBB
          css_fn = true, -- Enable all CSS *functions*: rgb_fn, hsl_fn
          mode = "background", -- Set the display mode.
          virtualtext = "",
        },
      })

I still see names highlighted

from nvim-colorizer.lua.

ehaynes99 avatar ehaynes99 commented on May 20, 2024

Hrmm, I have no idea where I got that... It does indeed work for me. @B4mbus I'm not sure what would be going on with yours. The place where it's determined is here:
https://github.com/NvChad/nvim-colorizer.lua/blob/master/lua/colorizer/matcher.lua#L71

Which, for some reason, also checks the css property, but I see you have that set to false as well.

from nvim-colorizer.lua.

gennaro-tedesco avatar gennaro-tedesco commented on May 20, 2024

I am having the same problem: names = false does not work (reproducing the same problem of the original plugin).

Likewise, it seems that the plugin does not attach to files automatically, rather it must be manually toggled all the times: perhaps this depends by how certain package managers (lazy.nvim in this case) load the configuration options?

from nvim-colorizer.lua.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.