Re: broken font locking in gdb-script-mode

[Stefan Monnier]

> AFAICS it never took line continuation into account.  I generalised the
> character set that a keyword can have.  It happens to include - / and =
> (and [0-9]).  If you had done:

> set args --foo --bar= \
>     baz --xyzzy=/some/path.ext

> baz would have had a keyword face.

Hmm... so keywords like /foo are possible?  Or is it only foo/bar (i.e. the
first char can't be one of / - or =)?  If the latter, maybe the patch below
will help.


        Stefan


--- gud.el      17 May 2006 17:49:29 -0400      1.106
+++ gud.el      18 May 2006 13:39:18 -0400      
@@ -3166,7 +3166,7 @@
 (defvar gdb-script-font-lock-keywords
   '(("^define\\s-+\\(\\(\\w\\|\\s_\\)+\\)" (1 font-lock-function-name-face))
     ("\\$\\(\\w+\\)" (1 font-lock-variable-name-face))
-    ("^\\s-*\\(\\(\\w\\|\\s_\\)+\\)" (1 font-lock-keyword-face))))
+    ("^\\s-*\\(\\w\\(\\w\\|\\s_\\)*\\)" (1 font-lock-keyword-face))))
 
 ;; FIXME: The keyword "end" associated with "document"
 ;; should have font-lock-keyword-face (currently font-lock-doc-face).