|
|
|
|
|
|
by Brian_K_White
886 days ago
|
|
|
I always felt sort of embarassed that I use mc 24/7 for everything. I live in it. It might as well be my login shell. I even use mcedit for about 80% of text editing outside of geany or codeblocks. I don't have any actual reason to be embarassed, since I'm actually perfectly comfortable in vi and and the command line on some old sco box without mc available, it's got to be just because I started among guys who themselves were even older unix guys who never touched anything like mc. Also it felt kind of like still using training wheels when I had been using xtree on dos before encountering unix. But hell I started on xenix myself and still miss some features from ksh93 vs the latest bash5. I haven't needed to live up to anyone else since forever. But embarrassed or not, I used it all day every day since the late 90's at work and home. It just makes the most sense to be using essentially a browser for that. For one thing I simply see more stuff. In the past, every day at work I'd see random junk left all over the place by other employees who clearly didn't even know that they had created these junk files and directories all over the place from having flubbed the syntax of command lines, or botched quoting or escaping inside programs they were writing. Files with names that looked like various other bits of command syntax from quoting mistakes etc. And still sitting there because if you don't actively ls, then you don't see it. I was constantly cleaning up stuff like that back before we finally went to individual developer vms. |
|
|
Also, a common usecase for me is having a folder full of files dumped together and I want to move some of them according to arbitrary criteria. Marking them with Insert in MC is so so much less work than typing everything.
Being good at something is also using the right tool for the job. CLIs shine at some things. TUIs and GUIs at others. They're complementary. It's not like one is better than the other.