public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Rename TUI status code to follow the docs
Date: Fri, 08 Dec 2023 10:43:31 -0700	[thread overview]
Message-ID: <20231208-tui-status-rename-v1-0-db019efd7483@tromey.com> (raw)

The TUI status window is called the "locator" in the code and appears
in tui-stack.[ch].  This has always confused me, and so I finally got
around to writing this series to rename both the files and the class.

---
Tom Tromey (2):
      Rename tui-stack -> tui-status
      Rename TUI locator window -> status

 gdb/Makefile.in                       |  4 ++--
 gdb/tui/tui-data.h                    |  2 +-
 gdb/tui/tui-disasm.c                  |  2 +-
 gdb/tui/tui-hooks.c                   |  2 +-
 gdb/tui/tui-layout.c                  |  6 +++---
 gdb/tui/tui-location.c                |  6 +++---
 gdb/tui/tui-location.h                |  6 +++---
 gdb/tui/tui-source.c                  |  2 +-
 gdb/tui/{tui-stack.c => tui-status.c} | 28 ++++++++++++++--------------
 gdb/tui/{tui-stack.h => tui-status.h} | 14 +++++++-------
 gdb/tui/tui-win.c                     |  2 +-
 gdb/tui/tui-wingeneral.c              |  2 +-
 gdb/tui/tui-winsource.c               |  2 +-
 gdb/tui/tui.c                         |  4 ++--
 14 files changed, 41 insertions(+), 41 deletions(-)
---
base-commit: 7543c960b00ddea23f6105eff4358ec214a7f93c
change-id: 20231208-tui-status-rename-ec68ef88991e

Best regards,
-- 
Tom Tromey <tom@tromey.com>


             reply	other threads:[~2023-12-08 17:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-08 17:43 Tom Tromey [this message]
2023-12-08 17:43 ` [PATCH 1/2] Rename tui-stack -> tui-status Tom Tromey
2023-12-13 13:35   ` Alexandra Petlanova Hajkova
2023-12-13 20:00     ` Tom Tromey
2023-12-08 17:43 ` [PATCH 2/2] Rename TUI locator window -> status Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20231208-tui-status-rename-v1-0-db019efd7483@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).