From: Eli Zaretskii <eliz@gnu.org>
To: Guinevere Larsen <blarsen@redhat.com>
Cc: markus.t.metzger@intel.com, gdb-patches@sourceware.org,
achronop@gmail.com
Subject: Re: [PATCH] Change message when reaching end of reverse history.
Date: Thu, 04 Apr 2024 15:39:22 +0300 [thread overview]
Message-ID: <86le5t7151.fsf@gnu.org> (raw)
In-Reply-To: <7d497864-4bef-4f95-bab5-1bf9cbee7000@redhat.com> (message from Guinevere Larsen on Thu, 4 Apr 2024 09:16:46 -0300)
> Date: Thu, 4 Apr 2024 09:16:46 -0300
> Cc: gdb-patches@sourceware.org, achronop@gmail.com
> From: Guinevere Larsen <blarsen@redhat.com>
>
> > If the above makes no sense, would someone please explain in more
> > detail what was the original issue, and I will try to come up with a
> > better suggestion.
> >
> The original issue is that when a user is in replay mode going forward,
> and they hit the message "no more reverse-execution history", some
> interpret that message as 'you can no longer execute forward' instead of
> the intended 'if you continue executing, we will do new things and
> record them, instead of just replaying what was already done'.
Then how about this instead:
End of recorded history; following steps will be added to history.
next prev parent reply other threads:[~2024-04-04 12:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-13 20:48 Alex Chronopoulos
2024-03-14 6:37 ` Metzger, Markus T
2024-03-14 10:26 ` Guinevere Larsen
2024-03-14 17:26 ` Alex Chronopoulos
2024-04-03 17:54 ` Guinevere Larsen
2024-04-03 21:15 ` Alex Chronopoulos
2024-04-04 6:22 ` Metzger, Markus T
2024-04-04 7:00 ` Eli Zaretskii
2024-04-04 12:16 ` Guinevere Larsen
2024-04-04 12:39 ` Eli Zaretskii [this message]
2024-04-04 17:26 ` Guinevere Larsen
2024-04-04 19:55 ` Alex Chronopoulos
2024-04-05 5:18 ` Metzger, Markus T
2024-04-05 15:43 ` Guinevere Larsen
2024-03-14 14:53 ` Tom Tromey
2024-03-14 16:13 ` Metzger, Markus T
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=86le5t7151.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=achronop@gmail.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=markus.t.metzger@intel.com \
/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).