4 ms·
What about adding "echo sleep 0.01 >> ~/.bashrc" to their .bashrc (or whichever shell config file is used)?
by ritter2a 5y ago
What about adding "echo sleep 0.01 >> ~/.bashrc" to their .bashrc (or whichever shell config file is used)?
- adwn 5y agoI don't get it. What's so bad/annoying about sleeping for 10 milliseconds whenever a new shell is opened? I don't think anyone would notice. "sleep 1000", on the other hand... EDIT: I misunderstood it as executing echo sleep 0.01 >> ~/.bashrc once instead of adding that line to .bashrc – even though that's exactly what you wrote...
- cto_of_antifa 5y agoWouldn't it add another ten Ms every time you opened a new terminal session?
- unionpivo 5y agoyeah its windows 95 simulator :)
- _flux 5y agoThe idea is to add the 'echo ..' to the .bashrc, not just run the command once.
- adwn 5y agoAh, now I get it. Thanks! That's evil, indeed.
- longwave 5y agoIt appends another sleep each time you start a new shell, so it subtly slows down over time.
- VHRanger 5y agowouldn't it do so exponentially? The first time it does it once, the second time the statement is there twice so it does it twice, then 4, 8, 16, etc. ?
- usrbinbash 5y agoNo, because; echo sleep 0.01 >> ~/.bashrc adds this to .bashrc; sleep 0.01 It doesn't add itself, so the sleep tie grows linear by 0.01sec each time a shell is opened.
- Tesl 5y agothe third time the statement is there three times ..
- happyopossum 5y agoNo, the entire statement isn't added each time, only the sleep portion.
- bilalq 5y agoThe real evil comes from putting it in ~/.bash_logout or equivalent so it doesn't get as much visibility as a bashrc might.