I don't know what exactly this will do, but I know enough about the terminal to get the feeling this is a bad idea
It searches for a process named vim using grep (which searches within provided lines), but since grep vim also contains vim, we then exclude grep too, so only the actual vim process gets found without the grep vim process. Sounds a lot like this post, doesn't it?
Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something
It'll give a list of processes with vim in the name. You could also just pgrep vim but that's too easy.
ps aux | grep vim | grep -v grepI don't know what exactly this will do, but I know enough about the terminal to get the feeling this is a bad idea
It searches for a process named
vimusinggrep(which searches within provided lines), but sincegrep vimalso containsvim, we then excludegreptoo, so only the actualvimprocess gets found without thegrep vimprocess. Sounds a lot like this post, doesn't it?Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something
It'll give a list of processes with vim in the name. You could also just
pgrep vimbut that's too easy.How'd you get my shell history?