[delish]

If you're like me, you'll think, "aliases!"

But, the shell is a bunch of nontrivial things to learn. Tools like Go Terminal_ could make a less discontinuous learning path for shell. I recently had to teach[0] someone a bit of shell, and I kept tripping over explanations of:

    command -[flags] arg1 arg2 arg3 | something else

Merely explaining that -xvf modified tar and how was a challenge. After I explained it, the user appended -xvf to cat in a different session. The above line would be a dozen lines of code in a blub. Shell takes a long time to grok.

All that said, I wouldn't call Go Terminal_ "efficient" ;).

[0] I did a terrible job.

[sdegutis]

> But, the shell is a bunch of nontrivial things to learn.

Yeah but if you're gonna learn this trade, you kinda gotta learn these things eventually, so why settle for a pacifier indefinitely?

[delish]

I should have been more explicit. I'm wishing for a less discontinuous shell-learning-path, meaning to say that you'd stick with Go Terminal_ until you found you wanted something that zsh or tmux or whatever offered you.

Everything I've learned in programming I've learned that way: do something the repetitive way until I notice it, then research or do something better.