history command never operates on a file, only on its in-memory history list. You can only read (
r), write (
-w), and append (
-a) that list to or from a file, and then access or manipulate the in-memory list. Reading from a file will replace or extend the history in your current shell session.
You can, however, spawn another shell and manipulate its history to run any command you want without affecting the history of your current shell:
bash -c 'history -cr file ; history'
( history -cr file ; history )
You can add any history options you want to the second
history command in either case. If you'll be doing this a lot, you may want to define a function accepting the file as an argument and running the subshell version:
( history -cr "$1" ; history )
If you're interested in displaying saved timestamps, you'll also need to set
HISTTIMEFORMAT. If you're using a subshell, and you get timestamps in your host shell, that should be there automatically, but for the
bash -c version or a script you'll need to set it:
bash -c 'history -cr file ; HISTTIMEFORMAT="%Y%m%d%H%I%S " history'
You can also
export the variable from the parent shell.
historyever operates on a file, rather than the in-memory history list. You'd have to append to/replace your current entries, or start a new shell. Is that workable for you?
catcommand, but because this history includes dates I get epoch times followed by the commands which I don't want. I probably have to write short utility for that.