This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [patch] Save the history by default
- From: Mark Kettenis <mark dot kettenis at xs4all dot nl>
- To: tromey at redhat dot com
- Cc: jan dot kratochvil at redhat dot com, gdb at sourceware dot org, gdb-patches at sourceware dot org
- Date: Wed, 9 Sep 2009 21:54:57 +0200 (CEST)
- Subject: Re: [patch] Save the history by default
- References: <20090908200537.GA14676__29508.7702492767$1252440377$gmane$org@host0.dyn.jankratochvil.net> <m3ws47q53t.fsf@fleche.redhat.com>
> From: Tom Tromey <tromey@redhat.com>
> Date: Wed, 09 Sep 2009 13:40:22 -0600
>
> >>>>> "Jan" == Jan Kratochvil <jan.kratochvil@redhat.com> writes:
>
> Jan> 2009-09-08 Jan Kratochvil <jan.kratochvil@redhat.com>
> Jan> Save the command history by default and use a file in $HOME.
>
> This idea is fine by me.
>
> I wouldn't mind changing other defaults too.
> We've discussed changing "set print object" a couple of times...
>
> I did not research this, but please make sure that this patch doesn't
> result in gdb saving history:
>
> 1. When in MI mode
> 2. When running the test suite
>
> Other than those possibilities, this seems fine.
>
> I think for changes to defaults it makes sense to wait a little while to
> let other maintainers speak up in case they have an objection. So
> please wait a little while before going ahead.
I have no objection to change *this* default since it doesn't really
change how you interact with GDB. But I'm far less enthousiastic
about changing things like "set print object" that affect the output
GDB generates for commands.