4 ms·
> It's mc and the command line. But does using both not mean one has to memorize more?
by jnxx 6y ago
> It's mc and the command line.
But does using both not mean one has to memorize more?
- BeetleB 6y agoOf course: In the same way as using fzf or zoxide means memorizing more. In the same way that using a modern shell means memorizing more. At my work there are a lot of people who don't know you can search your bash history with Ctrl-R because they learned the shell before that was a feature (or in most cases, before it was enabled by default). My point is that the separation between mc and the command line is an artificial one. If you don't want to learn, you can always stick to an ancient shell and not learn all the new features. If you are willing to learn, then don't make a distinction between mc and shell features. It's basically: Here are N new useful things to learn, and perhaps I'll want to learn some of them. It's not: Here are N shell features to learn, and M other tools to learn. Of course, you always have to ask yourself if learning it is a good use of your time. I myself have not learned any new shell featuresin a decade - I don't know what the new features are (I have, though, learned new shells). At some point, I realized there are too many things to learn and I need to strategize. I tried learning ranger a year or two ago. I definitely saw its power, but of all the things I wanted to learn, it was low on my list, so I dropped it. OTOH, I did learn dired recently, as I've always been a heavy Emacs user and I had neglected learning it all this time. mc is still better, though, but dired does have some capabilities that mc doesn't have. I started using autojump this year - now you tell me about zoxide. Maybe one day I'll look into it, but not today.