New feature proposal: cache input command & save them as history

[orsonzhai]

I use picocom for almost 10 years IIRC. In my case, I use it as a serial console tool for debugging the embedded boards.
Because the boards has no enough resource for history command storage, I have to input the same commands again and again after a reboot which maybe very frequently.
Is it a good idea to save all of them for later use at picocom side?
And an additional proposal is we can cache the input before pressing CR/LR key and send them all out at one time. It will be useful for some boards which has very short expire time when receiving inputs.
How do you think about these?

[wsakernel]

I had this problem as well. However, I don't think picocom is the proper location to tackle the problem. It would have issues: Linenoise only allows one history file, so input would be mixed with picocom-internal commands (not so bad probably). Cycling through the history would mean escape-key plus a second key. Not super comfortable. Deleting the current line and updating it with the next history item over a flaky serial line might generate artefacts resulting in modified items. Also, the history items will be clobbered with all your typos + backspaces to delete them, keys from prgrams you control with key presses (fdisk), etc...

I solved this by extending my terminal have multiple clipboards which I can copy/paste to/from. Works good enough and is even more generic because I can use it for my local shells as well.