From: Tom Tromey <tom@tromey.com>
To: Pedro Alves <pedro@palves.net>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH 3/5] Add "save user" command
Date: Mon, 30 Jan 2023 16:35:38 -0700 [thread overview]
Message-ID: <878rhjh9yt.fsf@tromey.com> (raw)
In-Reply-To: <1daf98a0-8568-8eac-310f-8688a611677d@palves.net> (Pedro Alves's message of "Mon, 30 Jan 2023 14:53:53 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@palves.net> writes:
Pedro> On 2023-01-29 4:21 p.m., Tom Tromey wrote:
>> PR cli/19395 points out that it would sometimes be convenient to save
>> one's user-defined commands to a file. This patch implements this
>> feature.
>>
>> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=19395
Pedro> Could we have a testcase for this?
Oops, I thought I'd written one.
Sure, will do.
Tom
next prev parent reply other threads:[~2023-01-30 23:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 16:21 [PATCH 0/5] Additions to "save" command Tom Tromey
2023-01-29 16:21 ` [PATCH 1/5] Save breakpoints so they are automatically pending Tom Tromey
2023-01-31 15:14 ` Alexandra Petlanova Hajkova
2023-01-29 16:21 ` [PATCH 2/5] Move show_user_1 to cli-cmds.c Tom Tromey
2023-01-29 16:21 ` [PATCH 3/5] Add "save user" command Tom Tromey
2023-01-29 16:57 ` Eli Zaretskii
2023-01-30 14:53 ` Pedro Alves
2023-01-30 23:35 ` Tom Tromey [this message]
2023-01-29 16:21 ` [PATCH 4/5] Add "save skip" command Tom Tromey
2023-01-29 16:54 ` Eli Zaretskii
2023-01-29 16:21 ` [PATCH 5/5] Add "save history" command Tom Tromey
2023-01-29 16:56 ` Eli Zaretskii
2023-01-30 14:50 ` Pedro Alves
2023-01-30 15:12 ` Pedro Alves
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=878rhjh9yt.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).