An alternative to making a shell script is to make an alias or a function instead. That way, it runs in your current shell session and you can access the history
command.
Additionally, you could always dump the output of the history command outside the shell script and then run the shell script on that file after you have dumped it.
I think the issue is that history
is a shell built-in and not an actual program (ie. external command) and it typically only works in an interactive shell session.
A workaround could be to access the $HISTFILE
directly:
{cat $HISTFILE | grep ...
Of course, you can use also just do:
{grep -e ... $HISTFILE | ...}
if you are opposed to the cat
at the beginning.
Not sure about studio quality, but for video conferencing and doing some Twitch streams, I’ve being using a Blue Yeti Nano USB microphone for a few years (since COVID) with no issues on Linux.