broken font locking in gdb-script-mode

[Nick Roberts]

 > gdb-script-mode seems to indiscriminately font-lock the first word of
 > every line as a keyword.

Yes, thats pretty much how it works

 > However it fails to take line continuation into account, so that in
 > the case of
 > 
 >   set args --foo --bar=baz \
 >    --xyzzy=/some/path.ext
 > 
 > both 'set' and '--xyzzy=/some/path' get highlighted, while only 'set'
 > is a gdb statement.
 > I'm reasonably certain this wasn't the case a while ago (a relatively
 > long while, I admit - I usually tweak .gdbinits in nano). Perhaps
 > previously the '-', '/' and '=' would have ended word matching, where
 > now only the '.' does?

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.


-- 
Nick                                           http://www.inet.net.nz/~nickrob