)]}'
{
  "commit": "907c06d0e4eb0bb9b7eb712d7d1018836bb52cc4",
  "tree": "79003a7015968df746ea835fb1f5b944b4eeac78",
  "parents": [
    "2707d55e539ef323dd14a1293e762bf3d9739ee7"
  ],
  "author": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Apr 07 22:27:39 2025 +0200"
  },
  "committer": {
    "name": "Tom de Vries",
    "email": "tdevries@suse.de",
    "time": "Mon Apr 07 22:27:39 2025 +0200"
  },
  "message": "[gdb/tui] Don\u0027t try deferred curses initialization twice\n\nI noticed that if deferred curses initialization fails, for instance when\nusing TERM\u003ddumb, and we try the same again, we run into the same error:\n...\n$ TERM\u003ddumb gdb -batch -ex \"tui enable\" -ex \"tui enable\"\nCannot enable the TUI: terminal doesn\u0027t support cursor addressing [TERM\u003ddumb]\nCannot enable the TUI: terminal doesn\u0027t support cursor addressing [TERM\u003ddumb]\n...\n\nI think it\u0027s better to try deferred curses initialization only once.\n\nFix this by changing bool tui_finish_init into a tribool, and using\nTRIBOOL_UNKNOWN to represent the \"initialization failed\" state, such that we\nget instead:\n...\n$ TERM\u003ddumb gdb -batch -ex \"tui enable\" -ex \"tui enable\"\nCannot enable the TUI: terminal doesn\u0027t support cursor addressing [TERM\u003ddumb]\nCannot enable the TUI\n...\n\nTested on x86_64-linux.\n\nApproved-By: Tom Tromey \u003ctom@tromey.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "491fcb18471f3940936ac3a69b7efe0b15e6e3ad",
      "old_mode": 33188,
      "old_path": "gdb/tui/tui.c",
      "new_id": "9f60e87e7886296d41799411fc595f6d4a403468",
      "new_mode": 33188,
      "new_path": "gdb/tui/tui.c"
    }
  ]
}