I just found out about gpp, which is a neat text preprocessor for quick and low-power templating. Which sparked me to look for other commands that ...
For further actions, you may consider blocking this person and/or reporting abuse
I am on Linux since 2005 and here's one of the most often used things:
I do
CTRL + Rto get the reverse CLI history, then I just type the first characters from:find . -type f -name ".*.sw*" -exec rm -f {} \;, find it then hit Enter.It finds all the .swp, swo, etc files left from my vim sessions and deletes them.
Also, big lol @
npm install kitchen-sink-robot-suit:-))That name surely needs a package!
You can also use the specific -delete action with
find.Good to know, thank you!
My favorite command I often forget about is
tee- used for simultaneously writing to the terminal AND to a file. It works best as part of a pipeline, which makes it a good fit for any shell supporting them - pretty much all the modern shells do now. I like to use this for verification: Did what my shell script print out match what I expect it to?It's not so much of a command but rather the concept of the | symbol. The pipe symbol is pretty a universal concept.
I use it in Powershell commands and Linux commands.
This Linux command gets a lot of use:
ps -ef | grep <'any string here'>
Or
history | grep <'whatever command I think I just ran'>
curl -vvvis helpful for learning and experimenting with all things http related.Not exactly a command, but favorite bad habit is running processes in the background with
slow_cmd &.The more I learn about curl, the more it blows my mind how powerful it really is.
With regards to backgrounding commands, I know about the ability, but I've never had an instance where I've thought to do it. What kind of commands do you find yourself backgrounding?
Mostly I background update commands when I first login. Definitely not a good habit but I always read the stdout.
flatpak update $yay &brew update &One of my favorites is an oldie but goodie, the table_print gem.
It allows you to print arrays of data out in nice tables
file command to know file format. Some times file name may contains wrong extension or doesn't contain extension. In this case file command really helps to know the format of the file. Below is the syntax.
file file_name
And below are some of results for file command.
"ASCII text" - normal text file
"ASCII text, with very long lines" - CSV file with large lines
"Zip archive data, at least v4.5 to extract" - ZIP file