ctrl+shift+p filters: :st2 :st3 :win :osx :linux
Browse

Colored Comments

Colored Comments is a SublimeText plugin to provide Comment Colorization

Details

  • 3.0.4
    3.0.3
  • github.​com
  • github.​com
  • 4 years ago
  • 2 hours ago
  • 5 years ago

Installs

  • Total 5K
  • Win 3K
  • Mac 786
  • Linux 882
Dec 22 Dec 21 Dec 20 Dec 19 Dec 18 Dec 17 Dec 16 Dec 15 Dec 14 Dec 13 Dec 12 Dec 11 Dec 10 Dec 9 Dec 8 Dec 7 Dec 6 Dec 5 Dec 4 Dec 3 Dec 2 Dec 1 Nov 30 Nov 29 Nov 28 Nov 27 Nov 26 Nov 25 Nov 24 Nov 23 Nov 22 Nov 21 Nov 20 Nov 19 Nov 18 Nov 17 Nov 16 Nov 15 Nov 14 Nov 13 Nov 12 Nov 11 Nov 10 Nov 9 Nov 8
Windows 0 1 2 0 1 1 0 0 1 1 2 0 1 0 1 2 0 1 0 1 0 0 0 2 1 0 0 0 0 1 0 3 0 0 0 1 1 3 0 0 2 0 0 0 0
Mac 0 0 0 1 0 0 0 0 0 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 0 0 0 0 0 0 2 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Linux 0 0 0 1 2 0 0 0 0 0 1 1 0 0 0 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0

Readme

Source
raw.​githubusercontent.​com

Colored Comments

The Colored Comments plugin was designed to help create more readable comments throughout your code. It was heavily inspired by Better Comments by aaron-bond

Global Settings

The following are global settings for ColoredComments - continued_matching - If enabled, the same match as the previous line will be applied to the next line if prefixed with a -

# TODO Highlighted as a TODO
# - This will also be highlighted as a TODO (Prefixed with a -)
# This will be an unhighlighted comment
# ! This is another comment
# - and again, continued highlighting

Version 2+

2020-03-06_21-11-38

New Highlights

Add new tags easily with the following format. Keep in mind the following:

  • identifiers: These can be plaintext or regex patterns. If they are regex be sure to set the is_regex property to true
  • is_regex: Set this to true if your identifier is a regex
  • priority: This setting is critical if you want to prioritize tag settings. Default: 2147483647
    • This should be used if there are multiple tags that could match on the same thing. An example of this would be "identifier": "*" and "identifier": "[\\*]?[ ]?@param" could both match on * @param because one is less precise. To avoid these conflicts you can give the [\\*]?[ ]?@param a higher priority such as "-1", Negative values get higher priority than positive values. If two or more tags get the same priority, they are treated as first come first serve type of matching.
  • scope: Are built in colors from your current theme. Scope takes precedence over Color
  • underline: Sublime API setting for region draws
  • stippled_underline: Sublime API setting for region draws
  • squiggly_underline: Sublime API setting for region draws
  • outline: Sublime API setting for region draws
  • color: Custom text colors
    • name: This is used when generating the scope for the color scheme
    • foreground: This is the text color
    • background: This is the background of the region, generally you'll want this to be your themes background color slightly changed background if your themes background is "rgba(1, 22, 38, 0.0)" this should be set like "rgba(1, 22, 38, 0.1)" for best results

Scope Examples

Taken from Sublime MiniHTML Reference

  • region.background
  • region.foreground
  • region.accent
  • region.redish
  • region.orangish
  • region.yellowish
  • region.greenish
  • region.cyanish
  • region.bluish
  • region.purplish
  • region.pinkish

Example Tag

"Important":
        {
            "identifier": "!",
            "underline": false,
            "stippled_underline": false,
            "squiggly_underline": false,
            "outline": false,
            "color":
            {
                "name": "important",
                "foreground": "#cc0000",
                "background": "rgba(1, 22, 38, 0.1)"
            },
        }

Contributors