▲ 1056 ▼ new rule (lemmy.world) submitted 2 years ago by kewwwi@lemmy.world to c/lemmyshitpost@lemmy.world 50 comments fedilink hide all child comments
[–] TheEntity@kbin.social 28 points 2 years ago (2 children) ps aux | grep vim | grep -v grep permalink fedilink source hideshow 4 child comments replies: [–] rockSlayer@lemmy.world 6 points 2 years ago (2 children) 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 permalink fedilink source parent hideshow 4 child comments replies: [–] TheEntity@kbin.social 25 points 2 years ago (1 child) 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? permalink fedilink source parent hideshow 2 child comments replies: [–] rockSlayer@lemmy.world 7 points 2 years ago Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something permalink fedilink source parent [–] Vash63@lemmy.world 9 points 2 years ago It'll give a list of processes with vim in the name. You could also just pgrep vim but that's too easy. permalink fedilink source parent [–] cheet@infosec.pub 1 point 2 years ago How'd you get my shell history? permalink fedilink source parent
[–] rockSlayer@lemmy.world 6 points 2 years ago (2 children) 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 permalink fedilink source parent hideshow 4 child comments replies: [–] TheEntity@kbin.social 25 points 2 years ago (1 child) 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? permalink fedilink source parent hideshow 2 child comments replies: [–] rockSlayer@lemmy.world 7 points 2 years ago Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something permalink fedilink source parent [–] Vash63@lemmy.world 9 points 2 years ago It'll give a list of processes with vim in the name. You could also just pgrep vim but that's too easy. permalink fedilink source parent
[–] TheEntity@kbin.social 25 points 2 years ago (1 child) 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? permalink fedilink source parent hideshow 2 child comments replies: [–] rockSlayer@lemmy.world 7 points 2 years ago Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something permalink fedilink source parent
[–] rockSlayer@lemmy.world 7 points 2 years ago Well that's anticlimactic. Here I thought grep would continuously ping ps aux and softlock the terminal or something permalink fedilink source parent
[–] Vash63@lemmy.world 9 points 2 years ago It'll give a list of processes with vim in the name. You could also just pgrep vim but that's too easy. permalink fedilink source parent
[–] cheet@infosec.pub 1 point 2 years ago How'd you get my shell history? permalink fedilink source parent
