-
Notifications
You must be signed in to change notification settings - Fork 161
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Command line history can grow exponentially #958
Comments
FYI, from the old Redmine issue tracker:
|
@ChrisJefferson moreover, even the test describing user preferences says "If this (i.e. saving history) is enabled it is suggested to set I think removing duplicates is too tedious. It is not possible to track reliably dependencies between different lines, and the result may no longer be consistent, so using it with |
@ChrisJefferson I've suggested alternative in #960 - please have a look. |
Resolved - the default length of command line history was set to 1000 in #960. |
I would like, preferably by default, to change
ReadCommandLineHistory
to remove duplicated lines, keeping the most recent occurrence of each statement.At the moment calling
ReadCommandLineHistory
repeatidly causes the history file to grow without bound, as the old information is concatenated onto the existing history. There is even a comment about this:For very long ⪆ sessions or if SaveCommandLineHistory and ReadCommandLineHistory are used repeatedly it can be sensible to restrict the number of saved lines
The only possible problem is, are some people relying on their command line history to contain exactly everything they ever typed, in the order it was typed in?
The text was updated successfully, but these errors were encountered: