bconsole: remove repeated successive entries from history. #1162
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
In
bconsole
, when you type a command multiple times in a row, all these entries are saved in the history and make previous command navigation annoying.Example: you do
run job=xxx <a lot of arguments> yes
and want to monitor the stats of the job, so you start typingstatus storage
every now and then to see how the job is behaving. Now you want to rerun the same job with the samerun job=xxx <a lot of arguments> yes
command, but it is buried behind multiplestatus storage
commands, and you would have to either press the arrow button up as many times as you entered thestatus storage
command, or have to do a search. This PR changes the behavior by making sure multiple same commands in a row are only saved once.Please check
If you have any questions or problems, please give a comment in the PR.
Helpful documentation and best practices
Checklist for the reviewer of the PR (will be processed by the Bareos team)
General
Source code quality
bareos-check-sources --since-merge
does not report any problemsgit status
should not report modifications in the source tree after building and testing