Files
go-highlite/syntax_files
Jesse Portnoy 449702f27b - Support df command
- Return warnings array from ParseSyntaxFiles() in addition to potential
  error. Not being able to parse the dir is a fatal error but if a
random file cannot be read, it should be considered a warning.
2023-07-18 18:46:01 +01:00
..
2023-07-16 23:44:37 +01:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2023-07-16 23:44:37 +01:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2023-07-18 18:46:01 +01:00
2023-07-16 23:44:37 +01:00
2017-03-30 10:33:52 -04:00
2023-07-17 23:52:44 +01:00
2017-03-30 10:33:52 -04:00
2017-03-27 20:47:03 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-02-16 19:27:32 -05:00
2017-03-30 10:33:52 -04:00
2017-02-17 10:13:08 -05:00
2023-07-16 23:44:37 +01:00
2023-07-18 18:46:01 +01:00
2023-07-16 23:44:37 +01:00
2017-02-17 10:13:08 -05:00
2017-03-30 10:33:52 -04:00
.
2023-07-17 04:00:50 +01:00
2023-07-18 03:59:23 +01:00
2017-02-18 09:45:07 -05:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00
2017-02-18 13:54:30 -05:00
2017-03-30 10:33:52 -04:00
2017-03-30 10:33:52 -04:00

Syntax Files

Here are highlights's syntax files.

Each yaml file specifies how to detect the filetype based on file extension or headers (first line of the file). Then there are patterns and regions linked to highlight groups which tell micro how to highlight that filetype.

Making your own syntax files is very simple. I recommend you check the file after you are finished with the syntax_checker.go program (located in this directory). Just place your yaml syntax file in the current directory and run go run syntax_checker.go and it will check every file. If there are no errors it will print No issues!.