From 1595c5ddda3016fbae889fb7186e0095082bf4e6 Mon Sep 17 00:00:00 2001 From: Dmytro Maluka Date: Sun, 24 Mar 2024 19:50:30 +0100 Subject: [PATCH 1/2] help/colors: remove "Syntax file headers" section The section says that users may use their own .hdr files for their own custom syntax files, which is simply not true. As a matter of fact, .hdr files are an implementation detail that doesn't need to be mentioned in the user documentation. --- runtime/help/colors.md | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/runtime/help/colors.md b/runtime/help/colors.md index 80a877d7..ae1a1236 100644 --- a/runtime/help/colors.md +++ b/runtime/help/colors.md @@ -359,16 +359,3 @@ example, the following is possible for html: rules: - include: "css" ``` - -## Syntax file headers - -Syntax file headers are an optimization and it is likely you do not need to -worry about them. - -Syntax file headers are files that contain only the filetype and the detection -regular expressions for a given syntax file. They have a `.hdr` suffix and are -used by default only for the pre-installed syntax files. Header files allow -micro to parse the syntax files much faster when checking the filetype of a -certain file. Custom syntax files may provide header files in -`~/.config/micro/syntax` as well but it is not necessary (only do this if you -have many (100+) custom syntax files and want to improve performance). From 984c32b513413e291bfef8026e4c3b0699178ce7 Mon Sep 17 00:00:00 2001 From: Dmytro Maluka Date: Sun, 24 Mar 2024 19:55:26 +0100 Subject: [PATCH 2/2] help/colors: add break before paragraph about colorscheme includes Make it a well-visible subsection of the "Creating a Colorscheme" section. --- runtime/help/colors.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/runtime/help/colors.md b/runtime/help/colors.md index ae1a1236..a1a0a98b 100644 --- a/runtime/help/colors.md +++ b/runtime/help/colors.md @@ -236,6 +236,9 @@ Here's a list of subgroups used in micro's built-in syntax files. * type.keyword (If you want a special highlight for keywords like `private`) In the future, plugins may also be able to use color groups for styling. + +--- + Last but not least it's even possible to use `include` followed by the colorscheme name as string to include a different colorscheme within a new one. Additionally the groups can then be extended or overwritten. The `default.micro`