-
|
I only have ever done minor tweaks to Micro's colorscheme files, and I am pretty bad at that. Nevertheless, I usually get around to what I want to do. However, recently, I have grown a desire for a more complete, colorful, and intuitive colorscheme and syntax highlighting when writing Here is how a dummy file looks with the default colorscheme and syntax highlighting (1185×501px): And here is how I want it to ideally look like (ignore the different tab sizing - 1674×892px): Would a modification of the syntax highlighting be necessary for me to create a colorscheme that would make it look like this? Are there some functionalities here that simply could not be reproduced? I would love to hear from people who know more about this than I do. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 7 replies
-
|
The current syntax for nix is pretty barebones so you would need to extend it. It should be straight-forward to recognize URLs in comments and move |
Beta Was this translation helpful? Give feedback.
-
|
Well, the yellow parts are optional, though, it makes it much easier/more accessible to see defined options in long configurations (and it just looks quite neat to me). I will look at other syntax files to see if I can modify the Nix one to be a bit better. Thanks for the input. |
Beta Was this translation helpful? Give feedback.
-
|
Making some progress, but I am not able to get the yellow things working, I can only manage to highlight everything (ignore the styling otherwise, I have not updated my colorscheme) 
|
Beta Was this translation helpful? Give feedback.
-
|
You could try something like this, it would color the last alphanumeric part before a - symbol.operator: "-"
- yellow: "[A-Za-z0-9_-]+\\s*(;|=)"
- statement: ";|=" |
Beta Was this translation helpful? Give feedback.
-
You know what? This almost work. We might be able to actually pull it off… 
|
Beta Was this translation helpful? Give feedback.
-
|
Progress is being done, I now basically only need it to ignore 
|
Beta Was this translation helpful? Give feedback.
-
Penultimate updateI now have it mostly working. With the following filetype: nix
detect:
filename: "\\.nix$"
rules:
- special: "\\b(null|self|super|true|false|abort)\\b"
- statement: "\\b(let|in|with|import|rec|inherit)\\b"
- statement: "[A-Za-z0-9_-]+\\s*(\ )"
- symbol.operator: "([~^.:;,+*|=!\\%@]|<|>|/|-|&)"
- symbol.brackets: "([(){}]|\\[|\\])"
- constant.bool.true: "\\b(true)\\b"
- constant.bool.false: "\\b(false)\\b"
- constant.number: "\\b[0-9](_?[0-9])*(\\.([0-9](_?[0-9])*)?)?(e[0-9](_?[0-9])*)?\\b"
- constant.string:
start: "\""
end: "\""
rules: []
- constant.string:
start: "''"
end: "''"
rules: []
- comment:
start: "#"
end: "$"
rules:
- todo: "(TODO|XXX|FIXME):?"
- underlined.url: "https?://[\\w\\-./?=&%#]+"
- underlined.url: "http?://[\\w\\-./?=&%#]+"
- comment:
start: "/\\*"
end: "\\*/"
rules:
- todo: "(TODO|XXX|FIXME):?"
- underlined.url: "https?://[\\w\\-./?=&%#]+"
- underlined.url: "http?://[\\w\\-./?=&%#]+"I am unsure if this is fully correct, as this is the first time I modify this kind of file, but it seems to work. Now, I still have not figured out how to make the last word yellow before the |
Beta Was this translation helpful? Give feedback.
-
|
This is now the bane of my existence. |
Beta Was this translation helpful? Give feedback.
-
|
This seems to mean that I am basically stuck with this at the moment. Which is probably still better than this In the first image, you can basically see every little issue properly:
|
Beta Was this translation helpful? Give feedback.
-
|
Simply doing I still have no solution for the other problem yet, though. |
Beta Was this translation helpful? Give feedback.
-
Yay.This is more a workaround than a solution, but replacing the problematic line with 
This is the full file for those interested: filetype: nix
detect:
filename: "\\.nix$"
rules:
- special: "\\b(null|self|super|true|false|abort)\\b"
- statement: "\\b(let|in|with|import|rec|inherit)\\b"
- identifier: "[A-Za-z0-9_-]+(\ *=|;|}.| &&|\\)|\ *\\(|\ *{)"
- symbol.operator: "([~^.:;,+*|=!\\%@]|<|>|/|-|&)"
- symbol.brackets: "([(){}]|\\[|\\])"
- constant.bool.true: "\\b(true)\\b"
- constant.bool.false: "\\b(false)\\b"
- constant.number: "\\b[0-9](_?[0-9])*(\\.([0-9](_?[0-9])*)?)?(e[0-9](_?[0-9])*)?\\b"
- constant.string:
start: "\""
end: "\""
rules: []
- constant.string:
start: "''"
end: "''"
rules: []
- comment:
start: "#"
end: "$"
rules:
- todo: "(TODO|XXX|FIXME):?"
- underlined.url: "https?://[\\w\\-./?=&%#]+"
- underlined.url: "http?://[\\w\\-./?=&%#]+"
- comment:
start: "/\\*"
end: "\\*/"
rules:
- todo: "(TODO|XXX|FIXME):?"
- underlined.url: "https?://[\\w\\-./?=&%#]+"
- underlined.url: "http?://[\\w\\-./?=&%#]+" |
Beta Was this translation helpful? Give feedback.
Yay.
This is more a workaround than a solution, but replacing the problematic line with
- identifier: "[A-Za-z0-9_-]+(\ =|;)""fixes" the issue (edit: and now quite a bit more detailed"[A-Za-z0-9_-]+(\ *=|;|}.| &&|\\)|\ *\\(|\ *{|\ *\")", will keep updating if needs be). It is not great and is fragile, but, in this case…hey, it works. Probably not going to open a pull request with that kind of quality, though.This is the full file for those interested: