Toolchain/binutils-gdb
1
0
Fork 0
forked from Imagelibrary/binutils-gdb
Code Pull Requests Activity

Make NEWS entry and manual regarding GDBHISTSIZE more consistent

Browse Source 
... by mentioning in the manual that setting GDBHISTSIZE to the empty
string disables truncation, like the NEWS entry does.

gdb/doc/ChangeLog:

	* gdb.texinfo (Command History): Mention that setting
	GDBHISTSIZE to the empty string disables history truncation.
This commit is contained in:
Patrick Palka
2015-06-17 14:44:38 -04:00
parent bc460514b9
commit 0eacb2983d
2 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
gdb/doc/ChangeLog
View File

@@ -1,3 +1,8 @@
2015-06-17 Patrick Palka <patrick@parcs.ath.cx>
* gdb.texinfo (Command History): Mention that setting
GDBHISTSIZE to the empty string disables history truncation.
2015-06-17 Patrick Palka <patrick@parcs.ath.cx>
PR gdb/16999

6
gdb/doc/gdb.texinfo
View File

@@ -22641,9 +22641,9 @@ Stop recording command history in a file.
Set the number of commands which @value{GDBN} keeps in its history list.
This defaults to the value of the environment variable @env{GDBHISTSIZE}, or
to 256 if this variable is not set. Non-numeric values of @env{GDBHISTSIZE}
are ignored. If @var{size} is @code{unlimited} or if @env{GDBHISTSIZE} is a
negative number, the number of commands @value{GDBN} keeps in the history list
is unlimited.
are ignored. If @var{size} is @code{unlimited} or if @env{GDBHISTSIZE} is
either a negative number or the empty string, then the number of commands
@value{GDBN} keeps in the history list is unlimited.
@end table
History expansion assigns special meaning to the character @kbd{!}.