[Bug gdb/16135] New: manual should explain/suggest the "set history filename .gdb_history" use case explicitly

["palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16135

            Bug ID: 16135
           Summary: manual should explain/suggest the "set history
                    filename .gdb_history" use case explicitly
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
          Assignee: unassigned at sourceware dot org
          Reporter: palves at redhat dot com

Changing the default command history save location to ~/.gdb_history
is being proposed, as a prerequisite to turning on history save by
default.

However, the use case of wanting to have history in ./.gdb_history,
as GDB currently does, will be a common one.  After the default location
switch the user that wants that can put:

   set history filename .gdb_history

in his ~/.gdbinit, and that will work with old gdb's too.

(Or put that in a PROGRAM-gdb.gdb file instead of ~/.gdbinit, though
that won't work with old gdbs).

The user can also do something like:

alias mygdb=gdb -ex "set history filename .gdb_history" in her shell,
and then run mygdb instead of gdb.

As we switch the default command history location, we should also
explain explicitly how to point the history file at ./.gdb_history, as
it may not be obvious to a newcomer that that is possible, and common.
We should have suggestions for handling this use case in the manual.

-- 
You are receiving this mail because:
You are on the CC list for the bug.