This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 5/7] PR gdb/15224 , Change the default set history filename to ~/.gdb_history.
- From: Pedro Alves <palves at redhat dot com>
- To: Eli Zaretskii <eliz at gnu dot org>
- Cc: mbilal <mbilal at codesourcery dot com>, gdb-patches at sourceware dot org, jan dot kratochvil at redhat dot com
- Date: Wed, 22 May 2013 18:24:13 +0100
- Subject: Re: [PATCH 5/7] PR gdb/15224 , Change the default set history filename to ~/.gdb_history.
- References: <51877A32 dot 1030503 at codesourcery dot com> <51877A99 dot 4060503 at codesourcery dot com> <51877B42 dot 7 at codesourcery dot com> <51877BC6 dot 6080007 at codesourcery dot com> <51877C76 dot 2000509 at codesourcery dot com> <518A0BA8 dot 9000703 at codesourcery dot com> <51936CAF dot 2090508 at codesourcery dot com> <51937A87 dot 2030403 at codesourcery dot com> <83ehd85q79 dot fsf at gnu dot org>
On 05/15/2013 02:26 PM, Eli Zaretskii wrote:
>> Date: Wed, 15 May 2013 17:07:35 +0500
>> From: mbilal <mbilal@codesourcery.com>
>> CC: <palves@redhat.com>, <gdb-patches@sourceware.org>,
>> <jan.kratochvil@redhat.com>
>>
>> On Wednesday, May 15, 2013 4:31 PM Eli wrote:
>>
>>> Any reasons why we should be changing the default? Is it bad to have
>> >a different history file in each project's directory?
>>
>> On Mon, 01 Apr 2013 14:29:30 +0200, Jan Kratochvil wrote:
>>> I see there should be also changed the default to:
>>> set history filename ~/.gdb_history
>>
>>> Otherwise it is a similar pain to ./.gdbinit, it is also non-standard to any
>>> other normal application which use history files in $HOME, I do not find using
>>> ./.gdb_history by default as acceptable.
>> All therequirement for this issue has beendiscussed here.
>>
>> http://sourceware.org/ml/gdb-patches/2013-04/msg00067.html
>
> Sigh... Another gratuitous backward incompatibility creeps in.
Keep in mind that history saving isn't enabled by default.
Would you prefer if we did something like:
At startup time, if "set history filename" hasn't been
used (tracked with a new global flag), then check whether there's
a $cwd/.gdb_history file, and if so, output a warning stating that
it's no longer read by default. The warning could also
suggest adding "set history filename .gdb_history" to .gdbinit
to get back the old behavior.
Thus if the user already has "set history filename ~/.gdb_history"
in .gdbinit she'll not see any warning.
But I'm really not sure it's worth the bother though.
--
Pedro Alves