From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: How to recall the commands run in previous gdb session?
Date: Mon, 30 Oct 2006 04:11:00 -0000 [thread overview]
Message-ID: <20061030041113.GA23811@nevyn.them.org> (raw)
In-Reply-To: <ulkmysawz.fsf@gnu.org>
On Mon, Oct 30, 2006 at 06:08:28AM +0200, Eli Zaretskii wrote:
> I agree with turning history saving on by default, but why change the
> location of .gdb_history? That'd be an incompatible change, and I
> don't see the justification for such a change. Do you?
I think that making GDB start to write temporary files in $PWD by
default would be extremely annoying. I'd end up with dozens of them
littered around my source directories and other places where they
aren't wanted (and probably get lots of bug reports from confused
Debian users about it). By analogy with bash, I figured $HOME would
be the right default location for history.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-30 4:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-29 20:35 Peng Yu
2006-10-29 20:49 ` Daniel Jacobowitz
2006-10-30 4:08 ` Eli Zaretskii
2006-10-30 4:11 ` Daniel Jacobowitz [this message]
2006-10-30 21:11 ` Eli Zaretskii
2006-10-30 21:13 ` Daniel Jacobowitz
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=20061030041113.GA23811@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb@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