⚠ warning: unexpected value for property “/ui/theme-defs/invalid-theme/styles/text/bad-property”
 --> {test_dir}/bad-config2/configs/invalid-theme/config.json:9
 |                         "bad-property": "abc"
 =   help: Available Properties
           color #hex|color_name
           background-color #hex|color_name
           underline 
           bold
✘ error: “abc(” is not a valid regular expression
 reason: missing closing parenthesis
 --> /ui/theme-defs/invalid-theme/highlights/foobar/pattern
 | abc(                                    
 |     ^ missing closing parenthesis       
 --> {test_dir}/bad-config2/configs/invalid-theme/config.json:14
 |                         "pattern": "abc("
 = help: Property Synopsis
           /ui/theme-defs/invalid-theme/highlights/foobar/pattern regular expression
         Description
           The regular expression to highlight
✘ error: “bad” is not a supported configuration $schema version
 --> {test_dir}/bad-config2/formats/invalid-config/config.bad-schema.json:2
 |     "$schema": "bad"                    
 = note: expecting one of the following $schema values:
           https://lnav.org/schemas/config-v1.schema.json
 = help: Property Synopsis
           /$schema <schema-uri>
         Description
           The URI that specifies the schema that describes this type of file
         Example
           https://lnav.org/schemas/config-v1.schema.json
⚠ warning: unexpected value for property “/ui”
 --> {test_dir}/bad-config2/formats/invalid-config/config.malformed.json:2
 |     "ui": "theme",                      
 =   help: Available Properties
           $schema <schema-uri>
           tuning/ 
           ui/ 
           log/ 
           global/
✘ error: invalid JSON
 --> {test_dir}/bad-config2/formats/invalid-config/config.malformed.json:3
 | parse error: object key and value must be separated by a colon (':')
 |                "ui": "theme",     "abc",     "def": "" }            
 |                      (right here) ------^                           
 |                                                                     
⚠ warning: unexpected value for property “/ui”
 --> {test_dir}/bad-config2/formats/invalid-config/config.truncated.json:2
 |     "ui": "theme"                       
 =   help: Available Properties
           $schema <schema-uri>
           tuning/ 
           ui/ 
           log/ 
           global/
✘ error: invalid JSON
 reason: parse error: premature EOF
 --> {test_dir}/bad-config2/formats/invalid-config/config.truncated.json:3
✘ error: invalid value for property “/ui/theme-defs/invalid-theme/styles/text/color”
 reason: invalid color -- “InvalidColor”
 |        reason: Unknown color: 'InvalidColor'.  See https://jonasjacek.github.io/colors/ for a list of supported color names
 --> {test_dir}/bad-config2/configs/invalid-theme/config.json:8
 = help: Property Synopsis
           /ui/theme-defs/invalid-theme/styles/text/color #hex|color_name
         Description
           The foreground color value for this style. The value can be the name of an xterm color, the hexadecimal value, or a theme variable reference.
         Examples
           #fff
           Green
           $black
✘ error: missing value for property “/log/annotations/org.lnav.test.no-condition/condition”
 reason: SQL expression is invalid
 |        reason: incomplete input
 |        --> /log/annotations/org.lnav.test.no-condition/condition
 = help: Property Synopsis
           /log/annotations/org.lnav.test.no-condition/condition <SQL-expression>
         Description
           The SQLite expression to execute for a log message that determines whether or not this annotation is applicable.  The expression is evaluated the same way as a filter expression
✘ error: missing value for property “/log/annotations/org.lnav.test.no-handler/handler”
 reason: no handler specified for annotation
 |        reason: Every annotation requires a handler
 = help: Property Synopsis
           /log/annotations/org.lnav.test.no-handler/handler <script>
         Description
           The script to execute to generate the annotation content. A JSON object with the log message content will be sent to the script on the standard input