Global syntax files?

[bartgrantham]

Is there a way to have a global syntax file for things I'd like to highlight in every file type such as:

• "TODO", "XXX", "foobar"
• background color of tabs
• trailing whitespace on lines
• trailing whitespace on files

Does micro merge multiple matching filetype syntax yamls? Could I just have a global.yaml starting with:

detect:
    filename: "^.*$"

...

Also, is there a documented set of keywords shared between the syntax and colorscheme sets?

Thanks in advance for your help, I'm really enjoying micro so far.

[usfbih8u]

I am also interested in a solution to add more words to the todo section of comments in a global way. Does anyone know of a solution? I want to avoid overriding all syntax files. Maybe there is some trick with 'include'?

It seems not possible, considering that each filetype has its own way of creating comments, but... To be more explicit, what I want to do is replace the 'comment' rules like this:

- comment:
    start: "/\\*"
    end: "\\*/"
    rules:
        - todo: "(TODO|XXX|FIXME|MORE|WORDS|HERE):?" # only change wanted

[Neko-Box-Coder]

Same here actually. I wanted to highlight NOTE in my files but don't really have a way to do it universally.

Also I always wanted to have the ability to add additional syntax rules for existing default syntax file without having to repeat what's in the default syntax file.

Maybe something like an additive syntax file that can be applied at the end over the existing ones would be great.

If enough people want this feature, maybe I can have a go at it at some point.

[usfbih8u]

The syntax part is my weak point in the editor, but I have a feeling that the include directive could be used/abused in some way.

For one of my plugins, I create a custom syntax for Markdown using a script that recomposes the syntax file to allow Micro to show code blocks with their own syntax.

You need to recompose because syntax files take into account the order of the rules. So all the languages available in Micro must be added before:

- special:
    start: "\`"
    end: "\`"
    rules: []

# accepts output file $1 where CONCAT the chunk and the language as $2
function output::lang_codeblock_chunk () {
cat << EOF >> "$1"
    - default:
        start: "\`\`\`$2"
        end: "\`\`\`"
        rules:
          - include: "$2"

EOF
}