You can also make searches interactive as you probably expect from history. So if you want to know the last command you ran in the ~/.ssh directory of your computer named FISHMONGER (we don’t judge), then you can search for that. The best part, though, is you can easily search through your history using all that information. In other words, you can see the directory you were in, the exact time and date, the system you were on, and the last return code of the command. It also provides context about commands you’ve executed in the past. However, Bashhub offers privately stored and encrypted history across machines. You might think you don’t need anything more than what you have, and, of course, you don’t. But did think about it and created Bashhub, a history database for bash, zsh, and probably some other shells, too. If you think about it, we have super fast computers with tons of storage compared to the “old days,” yet shell history is pretty much the same as it has been for decades. You can make them share history, but that comes with its own baggage. If you use a terminal multiplexer or a GUI, you are very likely to have many shells open. For one thing, by default, you don’t get history in one window from typing in another window. However, as I’ve mentioned in the past, bash history isn’t without its problems. It is, of course, enormously handy when you have to run something repetitively or you make a simple mistake that needs correction. Having a history of shell commands is a great idea.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |