public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
* [Bug gdb/15328] New: more powerful history manipulation
@ 2013-04-01 14:31 palves at redhat dot com
0 siblings, 0 replies; only message in thread
From: palves at redhat dot com @ 2013-04-01 14:31 UTC (permalink / raw)
To: gdb-prs
http://sourceware.org/bugzilla/show_bug.cgi?id=15328
Bug #: 15328
Summary: more powerful history manipulation
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: palves@redhat.com
Classification: Unclassified
I noticed there's no way to save the current GDB command history to some
specified file. Bash can do that with "history -w ~/foohistory". Maybe
gdb could have a "save history", as we already have the "save" prefix.
We have "set history xxx", and "show commands". I bet the latter would be more
discoverable if called "show history" or plain "history", as in bash.
Speaking of which, bash's "history" command allows several other manipulations
of history files:
$ help history
history: history [-c] [-d offset] [n] or history -anrw [filename] or history
-ps arg [arg...]
Display or manipulate the history list.
Display the history list with line numbers, prefixing each modified
entry with a `*'. An argument of N lists only the last N entries.
Options:
-c clear the history list by deleting all of the entries
-d offset delete the history entry at offset OFFSET.
-a append history lines from this session to the history file
-n read all history lines not already read from the history file
-r read the history file and append the contents to the history
list
-w write the current history to the history file
and append them to the history list
-p perform history expansion on each ARG and display the result
without storing it in the history list
-s append the ARGs to the history list as a single entry
If FILENAME is given, it is used as the history file. Otherwise,
if $HISTFILE has a value, that is used, else ~/.bash_history.
If the $HISTTIMEFORMAT variable is set and not null, its value is used
as a format string for strftime(3) to print the time stamp associated
with each displayed history entry. No time stamps are printed otherwise.
Exit Status:
Returns success unless an invalid option is given or an error occurs.
An idea would be to add a similar "history" command that models closely from
bash's.
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-04-01 14:31 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-04-01 14:31 [Bug gdb/15328] New: more powerful history manipulation 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).