From: "Eli Zaretskii" <eliz@gnu.org>
To: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfc/doco] bug reporting: mention 'script' command
Date: Fri, 18 Jun 2004 18:36:00 -0000 [thread overview]
Message-ID: <2719-Fri18Jun2004213221+0300-eliz@gnu.org> (raw)
In-Reply-To: <20040617205252.AC4A04B104@berman.michael-chastain.com> (mec.gnu@mindspring.com)
> Date: Thu, 17 Jun 2004 16:52:52 -0400 (EDT)
> From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
>
> Comments on the syntax?
None.
> Comments on the content?
Only one: I think it might be a good idea to add a "@pindex script"
entry before the new paragraph you added.
Btw, another way to record the GDB session is to run it inside Emacs
and then save the GUD (or shell) buffer to a file. On some systems,
such as Windows, it might even be superior to `script', since the
latteer, even if you find a Windows port and install it, might not be
able to cope with all the wird types of console output GDB and
inferior programs use on Windows, so part of the session might end up
unrecorded.
Thanks.
next prev parent reply other threads:[~2004-06-18 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-17 20:52 Michael Elizabeth Chastain
2004-06-18 18:36 ` Eli Zaretskii [this message]
2004-06-18 19:55 Michael Elizabeth Chastain
2004-06-19 8:32 ` Eli Zaretskii
2004-06-19 17:28 Michael Elizabeth Chastain
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=2719-Fri18Jun2004213221+0300-eliz@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=mec.gnu@mindspring.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