I love Midnight Commander so much; I install it on every system I use. It's so much more efficient/pleasant when in comes to navigating the filesystem and doing basic operations, especially when you learn the shortcuts and learn how to use it along with other command-line tools (hint: if you press Ctrl+O in MC it will switch to a normal shell command prompt it the directory you're in, and you can press Ctrl+O again to get back to MC; this allows you to easily use MC for things it is the most efficient for, and normal command-line for things where that is better).
I use it especially when moving files around in my NAS and it is awesome.
For GUI file managers, I have to say you can't get better than Dolphin. It has an integrated shell for the current directory, and you can split the view. It can also directly open ssh and SFTP URLs. For local things the combination of Dolphin and it's shell is unbeatable.
For some reason, the technical term for these is Orthodox File Manager, which I've always thought was an obscure cultural in-joke from the countries where these were most popular --- Eastern Europe and the former USSR.
The "orthodox" comes from a specific type of GUI, namely one that is driven by commands under the hood. UI elements are merely used to trigger commands that have the actual effect, and these commands could just as well be executed by hand, or automated into more complex commands.
This is an excellent way to build powerful UIs. It is what drives things like Vim, and often why Lisp-based software is so hackable -- think Emacs, StumpWM, etc. Instead of writing plugins against some small plugin API, you're wiring new functionality directly into the application.
The article you reference goes into more detail, as you say.
Does Blender also qualify? It even shows you the name of the Python function behind each UI element on hover, which is great for discoverability when scripting. Or maybe it used to, can't see it now.
At least in Russia, "orthodox" has an extra connotation that's not strictly coupled to church, akin more to "one true way", as in "orthodox way to learn a tech stack". With a negation, it becomes something like "wrong" or even "heretical", as in "pizza with pineapple".
What you're describing is the meaning of the word in English. I suspect using the word православный with this meaning started as a joke transplanting the English meaning of the word onto the corresponding Russian word.
"Orthodox" in Russian is "pravoslavny", literally "right faith" (pravyj = right, correct). I think it also contributes to the meaning. "The right way".
Means the same thing in Ireland too! My understanding is it derives from greek for “ordinary teaching” we also use the term heterodox for a cultural setting that encourages different types of thought.
The term Paradox is a challenging or somewhat contradictory idea.
We also use the term orthodox for a right handed boxer. “Southpaw” is non-orthodox left handed.
They were popular because there was no Unix culture in Eastern Europe at the time. Pretty much any computer geek was a DOS user. To me personally, it always seemed kind of lame because many of these people would not bother to properly learn the shell language.
I still have great affection for Midnight Commander, like Norton Commander before it. I used to use the latter to initiate a parallel cable connection to my brother's computer for Doom deathmatches, pretty cool for a file manager.
For no good reason, here's a screenshot of both of them running side by side on an iPad, which is a thing you can apparently do these days:
The thing about Orthodox File Managers when they first came about, that does not occur today, was the amount of time that had to be devoted to explaining that particular features would not work on OS/2, Unices, Linux-based operating systems, or Windows NT because only MS/PC/DR-DOS let programs do things like directly manipulate stuff in some other program's PSP or directly peek/poke video RAM or the keyboard buffer; or that filenames did not necessarily have "extensions"; or that there was more than 1 type of timestamp; or that links and symbolic links existed; or that different people can have different local times on a single machine; or that directories actually have sizes.
Today, the DOS Think is far less prevalent.
Midnight Commander's screenshots would have looked a little off to OFM users with DOS Think. Today, it's the original MS/PC/DR-DOS tools that will appear odd to novices. They did things like have a narrow 8.3 filename column, omit the dots, use graphics in the filename for system files, use glyphs that one could only obtain through poking C0-range codes into video RAM, change UI elements as one pressed and released the Alt key, and so forth.
For anyone looking for more modern terminal file managers: my favorite is yazi since it has great preview capabilities out of the box and requires zero config, but other alternatives are nnn, ranger, walk and lf.
Yazi is absolutely phantastic. It can be extended by own scripts. I have configured it to jump to any folder via fzf, find any file in a folder and subfolders via `fd`, and navigate to any folder/subfolder on my system in seconds. I don't use my GUI finders on my Mac anymore. Absolutely recommended.
This with the "Lynx-like motion" panel option and the "Quick view" enabled is the best way to review a source tree. So much so that the Debian ftp-masters use it and a plugin for doing license review of newly introduced packages.
`mc` was a gateway drug for me to switch from DOS to Linux in 1995. Because I hadn't been gotten comfortable with other text editors and file management commands yet, mc and its own text editor (mc -e) had felt very intuitive at the time. I felt at home. I was also amazed by stuff like FTP VFS support. It was so complete and done right.
I never could use mc. None of the keyboard shortcuts were at all intuitive to me, who had been using many different GUI file managers over the decades. Which is a shame, because I use SSH a LOT and doing normal file housework via pure CLI is super tedious and error-prone... Fortunately, I went looking more recently, and found the nnn file manager, which works properly with the basic keyboard commands I would expect, and really helped improve my workflow a lot:
I've been using `mc` for decades... In fact, in my early professional days as a software dev, I've written entire systems with PHP using `mcedit` (the built-in editor), because I didn't know `vim` then, and `mcedit` had syntax highlighting...
Mostly used Notepad++ or SciTE ( https://www.scintilla.org/ ) over the years, as the number of languages/platforms I traverse made it a consistent option for dealing with various document encodings etc.
I thought mc and mcedit was cool, but needed something small and portable within a fairly locked-down environment ( "No [root] for you!" as the admin would say.) =3
In a restricted environment like a console only system these two pane file managers are very useful. I was a heavy user of norton commander (nc) back in my DOS days. Also these are useful on mobile.
However I rarely use them on a graphical environment like windows where I can open arbitrary explorer windows and arrange them as I see like. I guess it depends on what people have experience on...
I never used MC (not very much into TUIs) but ages ago I wrote a graphical file manager in the same vein. For me the inspiration came from Directory Opus [1] on the Amiga, which was just awesome.
When GTK+ was released in the late 90s, combining my love of C programming with a newfound home in Linux and GTK+'s ability to make complicated graphical interfaces resulted in a dual-pane file manager. It was a great project.
For people on Android phones, Ghost Commander is neat.
For people who like the power of Emacs dired, there used to be Sunrise Commander but last I looked it wasn't so actively maintained and had some bugs, so I've sadly gone back to regular dired.
After moving from Windows to MacOS mc is the closest to Total Commander - the only software that I’m still missing from MacOS. Reminds me to DOS Navigator and Volkov Commander or even FAR
I just couldn't live without this thing. Well, I could but I would be less productive and more grumpy.
Back in the mists of time when dinosaurs roamed the earth and I developed DataEase applications under MS-DOS there was a thing called "Pathminder" [1] which was a very useful tool. Moving to Linux and finding Midnight Commander felt like coming home...
The killer feature in mc was the popup menu that you could configure to run several commands on the selected files. And if memory serves it could be customized on a global or directory specific way.
It seems nobody remembers the reason for the F-key assignment in the original i.e. Norton Commander... The assignment was very logical and easy to remember (and use) on the original PC keyboard, where F-keys were located in two columns on the left edge of the keyboard: F1, F2, then F3, F4, and so on. You can immediately see the advantages of the F9 location (the leftmost key at the bottom) and of the proximity of the Browse and Edit keys. I used my left thumb to press F10 - it was in the correct place almost without palm movement...
Nowadays I almost don't use Mc (except for file manipulation) because the Linux version has a serious weak point - it blocks the most important keystroke in shell: Tab. It is of course traditionally reserved for panel switching but this role could be deactivated when instead a single command line zone MC would allow to have a multi-line (in NC it was 3 or 4 line) zone for the shell scrolled display. This way it would be possible to have the full-size panel display (with the Tab switching panes) and one keystroke away reduced-size panels with full functionality of the shell tab key in the alternative panel mode...
Another disadvantage is the complicated way of changing settings (especially the colors and file attributes display format) in practice forcing trial and error mode... True, it's not needed often but spending hours on it is rather deterrent.
my one gripe after using mc for a few years is no parallel transfer support. it slows down significantly when transferring small files compared to one large file.
Unfortunately there were also badly written, overwriting viruses that destroyed the host.
I made a COM-to-EXE convertor back in time so that I can compress them with LZEXE (I don't remember anything about it, but I guess I just prepended an empty relocation table). It would have been interesting to incorporate that functionality in a virus.
Brings back memories. This is one of my older open source contributions that's still visible. I helped port it to a/ux in the early 90's. Line 98: https://fossies.org/linux/mc/AUTHORS
It was originally written by Miguel de Icaza who became a semi-famous for his work on Mono and others.
And who started Gnome Desktop! That always strikes me as funny. That he made the ultimate tool for in the terminal, and then move on to write a desktop environment
It was kind of the evolution of the time though. We were coming from dumb terminals hooked up to VAX/VMS and Ultrix boxes with kermit, to computers that had a tcp/ip stack and could actually do graphics.
You can, it even ships with two files you can use as examples in mc.{emacs,vim}.keymap. The vim one has my favorite comment in a config file:
[editor]
# No remapping, just use vim instead of mcedit
Given that you can specify the bindings config to use at startup with --keymap you can even configure task specific sets of bindings. This combined with extfs and custom menus makes it a great way to make a personal interface to non-file data sources too.
I haven't used this for a long old time. Back in the day it was the only way to recover your university dissertation when you'd rm -rf'd in the wrong directory.
Go on, ask me how I know ...
I've not had much cause to use it since then though.
Yeah, the answer was there in the question really :)
That was not a good day, about a week before submission was due. I unmounted the disk the second I realised what I'd done and started to look for guides on finding lost ext2 inodes. MC to the rescue!
Back in the 90s it certainly had some features that made it easier to do so, yes. On ext2 file systems (no journaling or other advanced features) it had some method to browse unlinked inodes that were still on disk so you could recover them. They’d then show up in “lost+found”.
If you were quick and unmounted as soon as you had realised what you’d done, and the space had not been re-used for anything, you could often get the file back because rm just unlinked the inodes on ext2 IIRC.
I imagine that the commands it used under the hood were accessible to anyone with the right know-how, but at the time that’s not something I had, and all the guides started with “use midnight commander” so I did :)
(Saying “only way” to recover might be a stretch, it’s true)
That should be doable with `kubectl debug ...` - e.g. attach an ephemeral sidecar container with mc to already running pod.
And you would ofc. configure that in K9S as a plugin to easily launch it :)
Fun fact (???) wayback about 40 years ago Central Point Software was humiliating Microsoft with its suites of utilities for Microsoft's OS's, which included file managers for Windows (and MS-DOS IIRC), and was a top rated #1 best seller. Microsoft graciously offered to buy a license for said software from Central Point, which they would make a standard part of windows. This was the kind of deal that practical realists tend to accept, even though it spells DOOM with a capital 3-finger salute. 'Tis great to see something as versatile as the wheel and axle or the Oklahoma speed wrench still rolling along.