public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/16135] New: manual should explain/suggest the "set history filename .gdb_history" use case explicitly
@ 2013-11-07 10:34 palves at redhat dot com
  2013-11-07 11:02 ` [Bug gdb/16135] " palves at redhat dot com
  0 siblings, 1 reply; 2+ messages in thread
From: palves at redhat dot com @ 2013-11-07 10:34 UTC (permalink / raw)
  To: gdb-prs

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.


^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug gdb/16135] manual should explain/suggest the "set history filename .gdb_history" use case explicitly
  2013-11-07 10:34 [Bug gdb/16135] New: manual should explain/suggest the "set history filename .gdb_history" use case explicitly palves at redhat dot com
@ 2013-11-07 11:02 ` palves at redhat dot com
  0 siblings, 0 replies; 2+ messages in thread
From: palves at redhat dot com @ 2013-11-07 11:02 UTC (permalink / raw)
  To: gdb-prs

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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |15224

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


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2013-11-07 11:02 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-11-07 10:34 [Bug gdb/16135] New: manual should explain/suggest the "set history filename .gdb_history" use case explicitly palves at redhat dot com
2013-11-07 11:02 ` [Bug gdb/16135] " palves at redhat dot com

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).