Re: [PATCH 5/7] PR gdb/15224 , Change the default set history filename to ~/.gdb_history.

Pedro Alves
2013-05-22T17:24:26Z

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