20

Would you like to browse history of the commands with their results what you typed last time to konsole?
Like packages what you upgraded, just to find out what failed or what were the results of the last few deep listings?

This is not same thing as "history" program does printing input history.
Or same as storing single input output by separately to direct it to text file.
Or exactly same thing as setting konsole scrolling size to unlimited and save manually.



The idea of this is to allow users itself have a change to check and search the actual and full history (input and output) of personal usage of konsole as it was saw by user then. And do it automatically so if the konsole window or tab gets closed, the output is saved, without "Damn, I forgot to save session history" -reactions right after closing.

It allows user to set how often konsole will create new log file and the path where the log files are stored. And the filename format what is used to save the file so user can later separate them more easily.

Other optional features for this is:

- How many logs are kept.
- What is max size for log until new one is created
- Log encrypting with Kwallet password

Security problems:

- Passwords (if not hidden like mostly are)
- Sensitive data (?)

script -c yourcommand does the job. no implementation needed. please refer to man script

sonay wrote:script -c yourcommand does the job. no implementation needed. please refer to man script

Not same thing.

You can not tell your mother/friend/student/any other support people to first start with script program.

The idea of this is to make it EASY for people to get automatic logging of everything what is on screen and not just push that to one file but actually allowing logging to different files depending different rules and it being a permanent.

Script does neither work every time well with different localisations and different bash setups. As it just simply records all kind non-sense as well there.

Yes, you could make complex .bashrc rule to start script everytime bash is started and then swap log file depending running program, time, tab, window, activity or so on. But really, who is going to write almost hundreds/thousands of lines for bash to get what is suggested here and being managed by non-geek user?

Many would love this just by enabling the logging on konsole and later when they need to give support over phone, they can even recall the last session log of changes or all last week changes.

In corporations and schools where commandline can be used by other purposes like teaching, it would help even more many where script is too complex and limited.

(yes, I have red a script man page)

Double post