)]}'
{
  "commit": "eefa43c9366e3665f1451d6bbfd46b84dea0d15d",
  "tree": "bed4944b487c08c98e5f89a6ed36e3edd4ca1304",
  "parents": [
    "fb8ea9d2ca2eafa83390d44d444d0193b32e19dc"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Oct 20 22:23:13 2023 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Fri Oct 20 22:23:13 2023 +0200"
  },
  "message": "[gdb/cli] Allow source-highlight to autodetect language\n\nCurrently when gdb asks the source-highlight library to highlight a file, it\ntells it what language file to use.\n\nFor instance, if gdb learns from the debug info that the file is language_c,\nthe language file \"c.lang\" is used.  This mapping is hardcoded in\nget_language_name.\n\nHowever, if gdb doesn\u0027t know what language file to use, it falls back to using\npython pygments, and in absence of that, unhighlighted source text.\n\nIn the case of python pygments, it autodetects which language to use based on\nthe file name.\n\nAdd the same capability when using the source-highlight library.\n\nTested on x86_64-linux.\n\nVerified that it works by:\n- making get_language_name return nullptr for language_c, and\n- checking that source-highlight still manages to highlight a hello world.\n\nReviewed-By: Guinevere Larsen \u003cblarsen@redhat.com\u003e\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n\nPR cli/30966\nBug: https://sourceware.org/bugzilla/show_bug.cgi?id\u003d30966\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "99be33348031ae9f9dd044d50a56e5c2ddd43d7d",
      "old_mode": 33188,
      "old_path": "gdb/source-cache.c",
      "new_id": "92acb10090130553a0d5c8e090d8fca379dc41d8",
      "new_mode": 33188,
      "new_path": "gdb/source-cache.c"
    }
  ]
}