From: Antonio Rische <nt8r@protonmail.com>
To: gdb-patches@sourceware.org
Cc: Antonio Rische <nt8r@protonmail.com>
Subject: [PATCH 0/2] Tab complete convenience variables
Date: Thu, 22 Aug 2024 15:47:37 +0000 [thread overview]
Message-ID: <20240822154730.1595141-1-nt8r@protonmail.com> (raw)
Implement tab completion for convenience variables. This has been
something that annoyed me about gdb for years.
Antonio Rische (2):
gdb: Do not create variables when parsing expressions
gdb: Tab complete internalvars in expressions
gdb/ax-gdb.c | 25 +++++++++++++++++++++++
gdb/cli/cli-utils.c | 2 +-
gdb/completer.c | 10 ++++++++++
gdb/expop.h | 48 ++++++++++++++++++++++++++++++++++++++++++++-
gdb/parse.c | 3 +--
5 files changed, 84 insertions(+), 4 deletions(-)
--
2.46.0
next reply other threads:[~2024-08-22 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-22 15:47 Antonio Rische [this message]
2024-08-22 15:47 ` [PATCH 1/2] gdb: Do not create variables when parsing expressions Antonio Rische
2024-08-22 15:47 ` [PATCH 2/2] gdb: Tab complete internalvars in expressions Antonio Rische
2024-08-22 19:41 ` nt8r
2024-08-26 16:54 ` Keith Seitz
2024-08-28 1:36 ` nt8r
2024-08-28 2:30 ` Eli Zaretskii
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=20240822154730.1595141-1-nt8r@protonmail.com \
--to=nt8r@protonmail.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