alternatively if you are really evil, you can 'alias ls="rm -rf"'
Sl: a steam locomotive in your terminal
51–58 of 58 posts
Re: Sl: a steam locomotive in your terminal
#52Oh come on! This isn't news. I was using sl fifteen years ago.
Re: Sl: a steam locomotive in your terminal
#53Re: Sl: a steam locomotive in your terminal
#54Great, excellent, fun. But, clearly, it should run 'ls' after doing its choo choo?
The Unix philosophy is that a program should only do one thing. sl only does one thing.
Re: Sl: a steam locomotive in your terminal
#55I did a little video on this a couple of weeks a go with a mini how to for Fedora users https://news.ycombinator.com/item?id=4766611
Re: Sl: a steam locomotive in your terminal
#56Earlier quoted context omitted.
Interestingly, at least how I have zsh configured and don't have bash configured, the behavior of `fg` after suspending these is different. With zsh when I resume the execution it continues looping. However with bash it resumes for only one more iteration.
Yeah I would have expected `fg` to continue the loop, but it doesn't. If I put `echo $?` after the subshell in that loop, it doesn't even print when I run `fg`. It's like bash just throws away the loop entirely when I suspend the subshell.
Yeah that's a famously annoying bug in bash.
Re: Sl: a steam locomotive in your terminal
#57> The following code changes the default behaviour of ls from listing > files to turning your terminal into an unstoppable steam locomotive. > The only way to end it is closing the terminal, so use this with caution. erm, that's easily stopped: [ctrl]+z $ pkill -9 sl
erm, no? "while true; sl; done"
erm, yes. I suggest you try it before commenting next time.
Re: Sl: a steam locomotive in your terminal
#58> The following code changes the default behaviour of ls from listing > files to turning your terminal into an unstoppable steam locomotive. > The only way to end it is closing the terminal, so use this with caution. erm, that's easily stopped: [ctrl]+z $ pkill -9 sl
^Z will just suspend `sl`, at which point bash will immediately launch another copy. That's what the loop is for.
Bash wont immediately launch another copy because the PID is still alive (even if it is stopped).