question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Out of the box] Enable color previewer/picker for plain-text in a temporary new file

See original GitHub issue

No issue here!! Just want to say that It took me an hour for a noob as so ordinary as me to read through the documents to do just a simple thing: Enable color previewer/picker for plain-text in a temporary new file Simply copy the below code into right handside of: Preference -> Packages Settings -> ColorHelper -> Settings That’s it! That’s all a noob needs to know to make life easier 😃 Well, in case you are as noob as me! lol

colorHelper-scanning

// Settings in here override those in "ColorHelper/color_helper.sublime-settings",

{
  "generic": {
        "allow_scanning": true,
        "scanning": ["-comment -string"],
        "color_class": "css-level-4"
    },

}

Issue Analytics

  • State:open
  • Created a year ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
facelessusercommented, Sep 23, 2022

You can just run the following command from the command palette: Color Helper: Override View's Scanning. I’m not sure if I documented it though…

0reactions
facelessusercommented, Oct 30, 2022

Override View's Scanning is view specific command that overrides a view on demand, so it cannot be applied globally.

Currently, there is no global way to force all views to show color previews except what is suggested in the OP. When doing what is done in the opening post, you don’t get too much language-specific control, so it’ll just show previews everywhere that are not found in strings or comments, but you can remove that requirement, or come up with a better generic rule if desired as well.

If there is a file type I prefer to have colors in all (or most of) the time, I simply add a new rule for that file type. If you truly want colors in all files, regardless of the language, then enabling scanning in generic via override is what you want. Then you can disable via Override View's Scanning only when you want.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Issues · facelessuser/ColorHelper
Sublime plugin that provides helpful color previews and tooltips - Issues ... [Out of the box] Enable color previewer/picker for plain-text in a...
Read more >
ColorHelper - bytemeta
ColorHelper fails if no syntax is assigned to output panels. · [Out of the box] Enable color previewer/picker for plain-text in a temporary...
Read more >
"access_policy.0.object_id" isn't a valid UUID on terraform ...
[Out of the box] Enable color previewer/picker for plain-text in a temporary new file, 8, 2022-09-23, 2022-12-09. ngclient: test data length limits ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found