-
Notifications
You must be signed in to change notification settings - Fork 8
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
HISTORY=ON improvements #125
Comments
Source indicates that HISTORY=ON,256 might do the trick (setting history to 256 bytes). The valid range seems to be 128-4096 bytes. But did not test it yet. |
|
According to the source code the syntax is more elaborate than the kernel's message suggests:
What are INSERT_STATE, SEARCH_STATE and MATCH_STATE remains to be found. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
HISTORY=ON
apparently allocates some 576 bytes of memory and use it to keep about 15 commands.It would be nice for this to be configurable. This would allow to lower the footprint on very, very restrained systems. For example on a 256K machine the user might prefer to set the history to 4 last commands, which would limit the memory usage yet still provide a history buffer that is comfortable most of the time. This could be configured for example through
HISTORY=4
("save last 4 commands only") orHISTORY=100
("use a 100 bytes buffer for HISTORY"), depending how the history logic is currently implemented.Another desirable improvement would be for the kernel to not store the same consecutive command. For instance running 3x
DIR
makes the command to appear 3 times in history.The text was updated successfully, but these errors were encountered: