Emacs自定义日志Major Mode语法高亮问题求助

Hey there! Let's fix those two issues with your custom log mode.

First, the problem with highlighting "*W", "*E", "F": the regexp-opt function with the 'words argument adds word boundaries (\b) around your patterns, but "" isn't a word character—so those boundaries don't match where you expect them to. We need to handle these star-prefixed markers separately without word boundaries.

Second, to highlight entire lines containing WARNING or ERROR, we'll add font-lock rules that match the full line and use the override flag to ensure the line-wide highlight takes precedence over individual keyword colors.

Here's the corrected code for your mylog-font-lock-keywords:

(setq mylog-font-lock-keywords (let* (
       ;; Word-based keywords (use word boundaries for precise matching)
       (x-keywords '("UVM_INFO" "NOTE" "Note"))
       (x-types-word '("UVM_WARNING" "xmsim"))
       (x-constants '("ACTIVE" "AGENT" "ALL_SIDES" "ATTACH_BACK"))
       (x-events '("at_rot_target" "at_target" "attach"))
       (x-functions '("llAbs" "llAcos" "llAddToLandBanList" "llAddToLandPassList"))
       (x-warnings-word '("UVM_ERROR" "UVM_FATAL"))
       
       ;; Non-word markers (no word boundaries—escape * since it's a regex special char)
       (x-markers '("\\*W" "\\*E" "\\*F" "\\*W,"))
       
       ;; Generate regex patterns
       (x-keywords-regexp (regexp-opt x-keywords 'words))
       (x-types-word-regexp (regexp-opt x-types-word 'words))
       (x-constants-regexp (regexp-opt x-constants 'words))
       (x-events-regexp (regexp-opt x-events 'words))
       (x-functions-regexp (regexp-opt x-functions 'words))
       (x-warnings-word-regexp (regexp-opt x-warnings-word 'words))
       (x-markers-regexp (regexp-opt x-markers)) ; No word boundaries here
       )
  `(
    ;; Highlight individual keywords first
    (,x-types-word-regexp . font-lock-type-face)
    (,x-constants-regexp . font-lock-constant-face)
    (,x-events-regexp . font-lock-builtin-face)
    (,x-functions-regexp . font-lock-function-name-face)
    (,x-keywords-regexp . font-lock-keyword-face)
    (,x-warnings-word-regexp . font-lock-warning-face)
    ;; Highlight the star-prefixed markers
    (,x-markers-regexp . font-lock-warning-face)
    
    ;; Highlight entire lines with ERROR/WARNING (override previous highlights)
    ("^.*ERROR.*$" 0 font-lock-error-face t)
    ("^.*WARNING.*$" 0 font-lock-warning-face t)
    )))

Key fixes explained: #

1. Star marker highlighting:

   • We separated the star-prefixed patterns into their own x-markers list, escaping the "*" with a backslash (since it's a special regex character).
   • Used regexp-opt without the 'words argument for these markers, so no word boundaries are added—this lets the regex match exactly where the "*W"/"*E"/"*F" appear in your logs.

2. Line-wide highlighting:

   • Added two new rules that match any line containing "ERROR" or "WARNING" (using ^.*ERROR.*$ to cover the entire line).
   • The 0 means apply the face to the entire matched line, and the t flag tells font-lock to override any existing highlights on those characters—so the whole line gets the warning/error face regardless of other keywords.

3. Order matters:

   • We placed the line-wide rules last. Since font-lock processes rules in order, this ensures the line highlight overrides any earlier keyword highlights for the entire line.

If you want the individual keywords to still stand out against the line background (instead of overriding them), you could use a background face for the line rules, like:

("^.*ERROR.*$" 0 '(:background "#ffeeee") t)
("^.*WARNING.*$" 0 '(:background "#fffccc") t)

Just adjust the color values to your preference!

内容的提问来源于stack exchange，提问作者rasmus