If you have fzf installed, it is easy to integrate it with your bash history.
In my .bashrc, I have:
# Introduce fzf-driven functionality as described here: https://wiki.archlinux.org/title/fzf.
source /usr/share/fzf/key-bindings.bash
source /usr/share/fzf/completion.bash
Also, you may be interested in zoxide, which keeps track of paths you have navigated to.
Also from my .bashrc:
# Enable an autojump-like 'j' command. Use 'ji M' to select paths starting with M using fzf.
# This needs to always come last.
eval "$(zoxide init --cmd j bash)"
I just started using both recently and it's great. For the fzf file search, there's even some extension that can show a preview pane of text files and even images!
$_ also works. I love Alt+. but sadly it doesn't work on any Mac terminal emulator I've found and, even more sadly, I am forced to use a Mac at work.
I haven't tried !$ so I'm not familiar with its function, but one nice thing about Alt+. is that you're not limited to the last argument of the most recent command; instead, it allows you to scroll backwards like Ctrl+R.
you can get a lot of the way there with Control+R reverse history search (mentioned in the article) -- and it's interactive. With fzf you can even get fuzzy history searching (the first search result has a video). atuin puts history into a proper db, optional syncs across hosts, and, like fzf, enhances control+r
I have a bash function in fuzzy_arg that I bind to Alt-a to uses fzf for interactively inserting arguments from previous commands. It's Ctrl-r for Alt-. -- I've found it super useful for essentially inserting partial commands (single arguments) from the history
is there a way to save commands from history? i tried to figure this out when i was starting to use linux regularly, to help learn commands and to make a reference for myself as to what the commands do. i'm familiar with things like man, info, tldr and others but i wanted to put things in my own words since i remember better that way.
what i'm wanting but can't seem to automate:
-save commands from bash history to a file with only the command and arguments used, no line numbers or time stamps.
-filenames can be kept, but if filenames are removable easily, that would be better.
-file saved in should have the list sorted with any duplicates removed and happen after any terminal session ends.
-i've read about changing the prompt but not done it correctly and not sure if possible or the safest way.
-i've tried using .bash_logout but it doesn't seem to do anything and i'm not sure why.
this isn't too important anymore, as i've grown more comfortable with linux and bash but it bugs me that i never got it to work. i can copy and paste more detailed notes of what i tried but i'd need to redact a bunch of cursing and frustrated whining.
yeah that looks exactly like what i wanted, thanks! i probably should have asked my question a couple years ago but i was still very new to linux and didn't quite know the lingo. i'm still not quite sure how < works in general but i get the pipe and other redirects at least.
putting it in .bash_logout doesn't always work. something involving login shells i don't quite understand yet but i'll read more about it. i saw mention of putting
exit_session() { . "$HOME/.bash_logout" } trap exit_session SIGHUP
in .bashrc to make it always work but i also don't understand trap yet either so i'll look into that too.
thanks again, your reply helped point me in the right direction of things i want to learn!