[Bug gdb/27040] New: Colors for class/keyword not settable

[Bug gdb/27040] New: Colors for class/keyword not settable

[jengelh at inai dot de]

https://sourceware.org/bugzilla/show_bug.cgi?id=27040

            Bug ID: 27040
           Summary: Colors for class/keyword not settable
           Product: gdb
           Version: 10.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: jengelh at inai dot de
  Target Milestone: ---

Created attachment 13028
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13028&action=edit
screenshot

gdb 10.1 is colorizing C++ keywords and so on, but I do not see a way to
override these colors.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/27040] Colors for class/keyword not settable

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27040

Tom Tromey <tromey at sourceware dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-12-11
                 CC|                            |tromey at sourceware dot org
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Tom Tromey <tromey at sourceware dot org> ---
Source code colors come either from GNU Source Highlight,
or from Pygments, depending on which one your gdb is using.

It probably makes sense to make it simpler for users to tweak
these.  I'm not sure how difficult that might be.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

[Bug gdb/27040] Colors for class/keyword not settable

[tromey at sourceware dot org]

https://sourceware.org/bugzilla/show_bug.cgi?id=27040

--- Comment #2 from Tom Tromey <tromey at sourceware dot org> ---
I looked into this for Source Highlight at one point, and I
think it would require gdb to make a style file and then
point the formatter at it.  It would be nicer if we could just
use some API for this, but I couldn't find one.

For Pygments we could probably write a Python class that did this.

-- 
You are receiving this mail because:
You are on the CC list for the bug.