[BUG] gdb-log: multi-line commands break hichligting and input requests are not highlighted correctly

[GitMensch]

Describe the bug
multi-line commands in gdb log are shown with a leading > which breaks its highlighting; also: after the >end the highlighting does not work any more and lastly: gdb prompts are colored, not sure if that's possible but don't highlight those (or using a dark gray) would be useful, at least the free standing " a " should not be colored.

Expected behavior

• similar highlighting to gdb syntax

log:

  (gdb) continue
  Continuing.
  ^C                                                                                                                                                                                                                                                                                 
  Program received signal SIGINT, Interrupt.
  0x9affb062b0f7 in testme () from /some/lib.so
  (gdb) commands
  Type commands for breakpoint(s) 4, one per line.
  End with a line saying just "end".
  >silent
  >break somefunc
  >end
  (gdb) break test.c:1098
  Breakpoint 5 at 0x7fffb062b0f7: file /tmp/test.c, line 1098.
  (gdb) c
  Continuing.

current highlighting:

as script:

continue
commands
  silent
  break somefunc
end
break test.c:1098
c

[pirpyn]

Sure, i forgot to handle the >.
About the commands info line being rendered as if it was gdb script, i never tought of that.

I don't have the bandwith right now, maybe in a few weeks