Go on, ask me how I know ...
I've not had much cause to use it since then though.
How do you know?
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!
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)
docker run --rm -it -v "$(pwd):$(pwd)" -w "$(pwd)" nixery.dev/mc mc $ rm -- -filename
where -filename is the file starting with a dash, and -- means "end of the command-line options".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.
This origin is elaborated at length here: https://softpanorama.org/Articles/introduction_to_orthodox_f...
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.
Orthodox = orthos + doxasia
Orthos = straight/correct
Doxasia = belief
orthodoxos = correct belief
The word “православный” in a meaning of some object/technology/way being good and true only started being used in Internet culture during 00s, and it still used, but as a slang/joke.
> "what is regarded as true or correct," from Late Latin orthodoxus, from Greek orthodoxos "having the right opinion," from orthos "right, true, straight" + doxa "opinion, praise".
(https://www.etymonline.com/word/orthodox)
But, when referring to dual-pane file managers, it's probably a mix of both meanings ("one true way" and "old-fashioned").
For me (native U.S. English speaker) the religious reference in "orthodox" is more transparent and that in "canonical" is more obscure, so "canonical" sounds more technical or more neutral somehow.
Ортодоксальный doesn't carry these connotations at all.
If anything, it describes something that is stuck in old ways and/or pointlessly rigid.
You describe it as not having this “one true way” connotation, but as having this pointlessly rigid connotation. In English, I think it has both connotations. Although, almost any phrase which has an implication of “one true way” can end up with a double meaning of “pointlessly rigid,” right? (It is context dependent, of course).
It can be contrasted against orthopraxy, right-practice, where the actions are more important than the belief or intent.
Based on the other comments here, these orthodox file browsers are based on a sort of underlying language,
https://news.ycombinator.com/item?id=45271878
> 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.
It… kind of makes sense actually, if we stretch the definitions a bit, haha. The orthodox UI has some button, which is translated into a sequence of commands that represent the actual user intent.
The alternative is just to have the button do the thing directly, there’s no description of the user intent other than what the button does. It is quite a stretch but maybe we could call that the an Orthoprax UI.
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.
20-25 years ago when this kind of file managers were all the rage for power users I was in a Fidonet/Usenet discussion group with the most fanatical of these users, often sysadmins, plugin devs, etc. I don't think "orthodox" was used as a term - sometimes it was used as an epithet, maybe, sort of a joke.
But I guess Dr. Nikolai shows us that if you are really committed to introduced a term you can do it, eventually :D
Also:
Now that I am more into the command line, I may need to give it a try.
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.
You could do the same with Nautilus. But in their infinite wisdom GNOME developers decided to remove that ability.
I like things that work. Somehow that makes me a luddite!
I wish mc could browse remote URLs, and I'm tempted to author an mc clone in Go to address this particular pain-point. Maybe some day handcrafting bespoke rsync/rclone commands will frustrate me enough to motivate me.
Try <https://krusader.org>. Same KDE underpinnings, but orthodox interface.
Very nice, but no longer as well maintained.
It doesn't simply select them like some other file managers do, it searches within the name and not just the prefix (again, like some other file managers), you don't have to press anything beforehand. When you get used to it, it's hard to go without it.
https://github.com/lxqt/pcmanfm-qt
For those preferring lightweight environments, it has far fewer dependencies than dolphin.
BTW, do you know if it can build for macOS, or is that a non-starter?
Because that's what I miss most in my shell.
print -rl -- *(om[1].)
in zsh?And of course, if the latest file isn't what I wanted, then it should be possible to easily go to the latest file before that.
$ date; print -rl -- **(om[1].D);date; newest -n4 -r0 $HOME
Wed Sep 17 12:48:53 EDT 2025
.config/mozilla/firefox/p9/bounce-tracking-protection.sqlite
Wed Sep 17 12:49:25 EDT 2025
/u/p9/.config/mozilla/firefox/p9/permissions.sqlite
/u/p9/.config/zsh/history
/u/p9/.config/mozilla/firefox/p9/places.sqlite-wal
/u/p9/.config/mozilla/firefox/p9/bounce-tracking-protection.sqlite
*newest -n4 -r0 $HOME
Time: 1.882365 (u) + 1.318166 (s)=3.215131 (99%) mxRSS 139 MiB
Not sure how to change to get most recent 4 or whatever in the Zsh style (since, you know, that'd be 10x slower..)I see it can even do file previews with kitty which is perfect as I already use kitty as my default terminal.
it was renamed somewhere around 1995
> ..a “Ctrl + dot” keyboard shortcut for opening the current directory in the terminal
https://9to5linux.com/gnome-49-brescia-desktop-environment-o...
Super nice especially when adding music to my library with Beets...
Better yet! (one-line) shell prompt is always available and has some nifty integrations via <Ctrl+X>. For example, one has a bunch of files visually tagged (selected) on current panel, and wants to tar them up as "/tmp/foo.tgz". Well...
tar czf /tmp/foo.tgz <Ctrl+X><T>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
(pun totally coincidental)
It was originally written by Miguel de Icaza who became a semi-famous for his work on Mono and others.
Starting when I wrote the Chess program that Apple distributed on their Apple II demo cassette tape, I have been interested in writing games for fun. Unfortunately, while I can code, I need artists and generally people with ‘game design style’ to do anything decent - I had that when I worked at Angel Studios.
Gnome is a parody of its former self.
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.
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.
https://lists.debian.org/msgid-search/20191228133344.GA4943@...
I moved from England to Czechia in 2014 and was amazed to discover almost everyone used them. My first job in a Windows company, it had a site licence to Total Commander, and it was preinstalled on all machines.
When I told them I found the Windows Explorer to be perfectly fine, people genuinely gaped in amazement at me as if I said I chose to type with my feet or something. But I do. It's very keyboard-controllable, and was fast and efficient until MS started to cram the ribbon UI into it. Since Windows 8 it's been destroyed.
I used the Windows 3 UI, complete with File Manager, until 1996. I didn't mind it at all. But I thought the Windows 95 Explorer was an amazing tool when it was launched, and as soon as Win NT got Explorer with NT 4, I switched to it.
I have never been unhappy.
I can tile 2 windows side-by-side in moments if I want that old source-and-destination layout. It works absolutely great.
I tried Total Commander, and Midnight Commander too, and they don't do anything I can't do in seconds anyway. I really don't get it. It's not that I dislike them, but I am perfectly happy with the replacement.
I am not saying anything is wrong with the OFM model but when it went away in the OSes I used 30 years ago, I didn't miss it.
Delighted to find there are some Linux versions!
It now even supports true keyboard reporting (through Kitty TTY protocol on compatible terminals) for SSH connections.
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...
They're exactly the same as Norton Commander had been since the 80s.
It sure is a generational thing, I have the same problem with Emacs. But not with Vim.
For example i've worked three Polish gamedev companies and in every single one of them most people (including people who weren't even born in the days of Norton Commander) used Total Commander (it is GUI-based but the shortcut keys and overall layout are almost the same).
(FWIW Notepad++ was ubiquitous too)
I'm using GUI File Manager only for multimedia (photos, movies, pdf files).
This isn't possible in MC. And also a concrete parallelization is not available. This sounds like a feasible feature request to the upstream MC project! I'm sure Gnu Parallel or just pure C code would be able to handle parallelization of copy jobs.
EDIT: Wait! It does have background transfer now. Which means my technique of how I do it in Total Commander will work in MC now as well. It is almost like having Parallelization.
[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.The command to install it is:
brew install mc
I don't know anything about Emacs =)
brew install mc
The Midnight Commander web site says to use
% brew install midnight-commanderWhen 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.
Edit: Incorrect:(I'd guess the biggest requested change would have been to update it from using GTK 2 to GTK 3, but I can definitely understand why someone wouldn't want to...)
I thought I had released the GTK 3.x version, but I guess not, then. It might have been that there was something I just couldn't get to behave right, gentoo is somewhat picky about its UI and tries to make it do the right thing in ways that GTK sometimes isn't ready for.
Today I guess the target would be GTK 4.x, I tried to align with the latest main version back when I was maintaining it more.
Oh and 2016 makes sense, had my first kid in 2015 ... :|
My bad. You had. Sorry.
> Oh and 2016 makes sense, had my first kid in 2015 ... :|
Much congrats!
Just take a look at that feature set. All in 26.58MB. The average modern web site weighs more than that.
PathMinder pre-dates Norton Commander by two years:
Pleasantly surprised to see this topping HN today, and even more than the project and its website are still maintained in 2025.
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...
Specifically I believe this:
=P
Is a tongue-in-cheek emoticon, but I can see how it can be mistaken for a mobius strip emoticon.
I’ve been trying to get used to ranger since I’m learning vim anyway
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:
https://pbs.twimg.com/media/GYRYTq6WUAAt_1t?format=jpg&name=...
Dude, plug that thing in!
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.
See `cat "$( which ranger )"` for what it does, but TLDR lets your shell `cd` (navigate) to the directory where you've navigated to within ranger. (ie: you can use the alias `r` as a lazy man's `cd`).
It has to be done as a shell alias b/c `$PWD` is exclusively a shell concept, can't be modified by a mere program that you're running (thankfully).
Other useful bits are sometimes `F2` for interactive file-rename (eg: backspace `.txt` to `.csv` or whatever), mark/tag support so `'d` goes to `~/Downloads`, `'g` goes to `~/Git`, `'t` for `/tmp`, etc.
Overall if you're decent at vim there's a lot to love, and otherwise the basics pretty much work like you'd expect with keyboard/gui conventions (arrows, f2, etc).
Still use mc in 2025 :-)
The only time I ever have to use the mouse in WE is when I try to move to the Quick Access side-bar: sometimes focus gets lost somewhere around all the bloody menus I never use and I can't place it where I want it. It's weird and I'm not describing it clearly because it happens only occasionally and I don't understand exactly how.
I know many people think these things don't matter, because you can do everything with MC (and more), but I disagree. In this case, every fraction of a second matters. In the setup I described above, selecting all files in the current directory and moving them to the directory in the other pane is: one flick of the right hand (roll over + and Enter on the numpad), F6 with the left hand followed by another Enter immediately with the right hand. Now try to do that using the + that is on your = key and tell me it's the same thing.
Well, and monitor.
If you're slouching over your laptop for extended periods of time, you have bigger problems than not being able to use numpad +...
That was not true otherwise you wouldn't get stuck with the most unergonomic keys mandating moving your hands off their resting place.
> selecting all files ... : one flick of the right hand
The common Ctrl+A is better, no flick, just shifting a single thumb
> F6 with the left hand followed by another Enter immediately with the right hand
Or still same single hand Ctrl+Shift+X (or something even easier like maybe X, X)
Touch typists always have to get their dig in.
I've been using vim for 5 years now and still use up/dn/lf/rt - it's easier to find in a tactile manner with the right keyboard and makes MUCH more sense to the brain than hjkl. It's like 80ms travel, worst case.
Even the gaming community got this more correct with wasd, in terms of key positions that make sense to the brain.
It isn't because your resting keys require NO finding, so will always be easier.
> makes MUCH more sense to the brain than hjkl > Even the gaming community got this more correct with wasd, in terms of key positions that make sense to the brain
Don't repeat the ancient hjkl mistake? What does your brain say to this simple counter? But more importantly, how does any of the numpad+/F6 nonsense follow from the fact that you can improve within the letters?
> It's like 80ms travel
I bet you didn't really time anything in real use, especially not the return timing to go back to the base, which will take you longer. But more importantly, go convince the "every fraction of a second matters" guy first. To me the lack of design logic/convenience is enough.
You still need to find them unless your hand is glued to the resting keys and even if it were the resting keys might not be hjkl, and even if they are they will by default type hjkl and not move the cursor in any other software you ever use except vim.
(It can't be objectively measured of course but I am convinced anyone who can use vim without thinking has spent more time learning vim than they gained from using vim for other things) ;-)
It is, the hint is in the name!
> even if it were the resting keys might not be hjkl
So? Use the other resting keys, resting is key here, not their labels
> even if they are they will by default type hjkl and not move the cursor in any other software you ever use except vim.
Sorry, but your knowledge of the software world is too shallow, there are other apps that do that, specifically, file managers.
Also you can use them universally in all apps with an extra modifier (right alt to do everything with a single hand), so
> gained from using vim for other thing
will literally include every single app that uses cursor keys
Just about any line of text I write daily uses symbols not reachable from the resting position, and once my hand has left that position the arrow keys are easier to find. (Inverted T of course, with home/end/pgdown/pgup cluster).
>there are other apps that do that, specifically, file managers
The point is that you ("you" in this case being a typical user, not you personally) will open applications every day where hjkl does nothing at all with the cursor, and you have to use the arrow keys anyway. This is mental friction that remains even after you spent years internalizing the hjkl cursor moving flaw.
Faced with this situation a user can choose to either use the arrow keys in vim, or go full Stockholm syndrome and change the default in every other piece of software to match vim.
If that seems like a good idea, it might be worth remembering that the creator of vi didn't choose hjkl because he thought it superior to using arrow keys - he did it because the computer he used had no arrow keys! ;-)
Use a better setup! No-one forces you to use bad defaults and think everything must be bad. Also, there are no such symbols even on standard setup, all of the number row keys/symbols are reachable with individual fingers, so you never miss the resting place, it's a couple of fingers moving back and forth.
> my hand has left that position the arrow keys are easier to find. (Inverted T of course, with home/end/pgdown/pgup cluster
It didn't, a couple of your fingers did. But also, why did you ignore the F6, numpad+ etc hand dance and only focus on the arrow keys?
> "you" in this case being a typical user
A typical user doesn't use vim. A real user using vim is perfectly capable of basic keyboard rebinding
> This is mental friction that remains even after you spent years internalizing the hjkl cursor moving flaw.
No, it goes away after you spend minutes oiling your system to remove friction. (Of course, it may still take years of ignorance before that...)
> change the default in every other piece of software to match vim.
Or you change the default once system-wide. See, reality is much simpler than your fantasy!
> the creator of vi didn't choose hjkl because he thought it superior
So? You're the only one here stuck on hjkl because for some reason you can't comprehend that it's just a config, not a mandatory commandment passed down by the Vim prophet.
Even if you only use your own computer, customizing the basics is a bit of a trap in many ways.
First you need to find a different setup that is actually better, not just different. Then you need to build muscle memory for it, then you need to never use any other computer because they will not have your setup.
I think getting good at using the defaults is better than changing the defaults. Basically learn to play the guitar, even if it's hard.
I customize things too, but take care to make it additive, not transformative. Aliases, plugins, better software and such are fine, but messing with my muscle memory is just not worth it.
>Also, there are no such symbols even on standard setup
That depends on the standard. In some countries you need two hands to type an @, just to take one example. For US english the numpad is a good example though. Not so easy to find the home keys from the numpad, but your hand passes the arrow keys on the way. :)
>why did you ignore the F6, numpad+ etc hand dance and only focus on the arrow keys?
Because I'm mainly making a counterpoint to your claim that using hjkl was better than using the arrow keys.
It has admittedly grown to a more general anti-bikeshedding rant fuelled by my own bikeshedding regrets - so I better stop here. :)
Again, if you really had such a defeatist attitude to changing things you'd simply never vim, or the MC file manager for that matter because they're not available everywhere, and you need to avoid other computers etc. In reality all of this is false, of course, humans are flexible enough
> but messing with my muscle memory is just not worth it.
You don't have any muscle memory for F6. But also it's trivial for such common things as cursor keys alternatives, you ijkl is already an inverted T that your muscles are used to, just without the extra hand move
> That depends on the standard. In some countries you need two hands to type an @, just to take one example
Wrong again, you'd need two fingers, but your hands stay near their resting place.
> Because I'm mainly making a counterpoint to your claim that using hjkl was better than using the arrow keys.
You're the one who brought these keys up! My point was "Don't repeat the ancient hjkl mistake?", but then you couldn't argue with.
hjkl makes a ton of sense considering the j key on all keyboards has a tactile feel, it is way easier than arrows which are a whole lot more than 80ms travel for the move + finding the home row again.
but you're probably just rage baiting
esdf would be better (using stronger fingers). I don't like hjkl either and would use ijkl if I were non-lazy enough to figure out rebinding. I can remember many games for the Apple ][ used ijkm.
btw this is why vi used hjkl for navigation: https://catonmat.net/why-vim-uses-hjkl-as-arrow-keys
Yes, but they would while editing text, and the context of this was the idea of drawing inspiration from other control systems for a text editor UI.
The choice of key labeling on that terminal implies that there was a pre-existing convention, but the article doesn't go into any detail about that.
My Midnight Commander 4.8.33, however, remember previously entered mask, and if no mask was entered - then it defaults to selecting nothing :(
It's not mc's fault, the Escape delay is added by the terminal emulator, to correctly handle escape sequences. You can probably configure it, but the most portable way that works everywhere is to simply press it twice quickly. It's only barely slower than the DOS way of doing it, and much faster than pressing and waiting for a second.
I'd probably tune the delay to 100-200ms if I ever really felt it and have the option to change it.
I'm not sure if midnight commander was a complete rewrite.
In case you do prefer GUIs, consider DoubleCommander.
is it nostalgia, or is it really that useful?
Personally I really want to like Midnight Commander, well I do like it, I just don't use it that much. As someone else pointed out, the keyboard shortcuts just doesn't work for me for some reason. I think if you grew up using the F-keys a lot, then it probably makes total sense.
I have plenty of criticism for MC, I wish it had the sufficient amount of features so that it becomes a better representative of its genre and I could start recommending it to other users. Krusader and Total Commander are lightyears ahead, try these first.
I came from C64 where I had GEOS, that allowed me to do anything with a nice GUI, so it felt like quite the step back.
However, PCs were all the rage at that time, so I got one and thanks to Norton Commander, I was able to use it with a nice(+ish) GUI too.
Somehow during my 30+ years *nix career I never truly and actually used mc. Seems like moving files around in shell is good enough.
I ended up being on a Linux fork of Far Manager, which works beautifully: https://github.com/elfmz/far2l
Of course mc and far can be used over an SSH connection, so they have their advantages too...
If you wonder how to quit (if started from a terminal):
It's `ESC 0`. Or "exit" like from a shell. Took me some time I have to admit (q, ctrl-c, ctrl-q, F10, ESC all did not work).
If that fails, you can click on "10 Quit" with the mouse (not ideal, but an immediate solution).
I've been working on "F2 Commander" on and off for a while now. At first, I wanted a TUI to view the contents of cloud storage buckets (GCS, S3, etc.), but it quickly evolved into an orthodox file manager. The funny thing is, the first version was in Common Lisp, but then I discovered Textual and was instantly sold on it - it's really fun to work with. The app scratches my itch, and although most of the time I myself prefer just using the regular command line, I open it up when I need to quickly navigate or move some files in a complex directory tree.
What I never got was why this style of TUI (MS edit.com, qbasic, etc) isn't really carried through in modern tradition? I really enjoyed these when when I was younger... yet even textual or ratatui apps don't really bring this interface to the terminal. (Or why screen-coordinate-based terminals aren't the norm to base TUI apps upon... this aspect just seems "obvious" but in this aspect modern terminal emulates seem lightyears behind MS-DOS, of all things).
Perhaps the rewrite of edit [1] will spawn a ressurgence of this TUI style?
[1] https://devblogs.microsoft.com/commandline/edit-is-now-open-...
You can do this to get information on how to download it:
curl 'gopher://sdf.org/0/users/jmccue/repository/dm220.txt' > dm220.txt
I use it for SCP and S3 file management too (first mounting the folder using sshfs or goofys).
<F6><Tab>, <F6><Tab>
I like to move it, move it!
<F6><Tab>, <F6><Tab>
Move it!
But somehow the reality of how I - and I think most people - use computers today is very different. I don't find myself navigating a shallow directory hierarchy and making file operations too often. A part of it is that all the stuff is in the cloud or at least connected to applications (eg: I am more likely to navigate my coding projects from an IDE than from Shell/MC)
And when I administer eg my home linux system, it seems more likely that I jump to a random far-away directory or edit a specific file, rather than navigating the filesystem MC stye.
I am curious how people are using computers today that MC-like interface is still most suitable.
- Actually letting you navigate the directory structure.
- Making WSL volumes easy to work with.
- Keyboard accessibility.
- Dealing with many tabs and bookmarks.
- A stable interface that doesn't randomly change without my consent.
- Many other things I'll omit for time reasons.
- Synchronize directories (symmetric and asymmetric, with subdirectories).
- Background operations.
- Operation queue (so that you don't thrash disks while doing many operations).
- Start menu.
- Displaying directory sizes easily.
- Great file search.
- Diff viewer for text files.
- F3 quick file viewer.
- Compare directories.
- Plugins.
Those are my favorites.
On linux I use it to manage remote servers without a window manager (by design, because I don't need one).
I also use it to pass files between my laptops over ssh, between windows and/or linux.
Recursively find files -> Panelize alone is worth the price of admission.
Multi-file select.
Two-panel for easy moving/copying files, including to cloud/remote/ssh drives (just mount them).
Quickly go back to previously visited folders in your history.
Compare folders.
etc etc
> I jump to a random far-away directory
Esc-C and type in the path. I do it all the time in MC.
> or edit a specific file
Navigate to folder (above), type first letters of filename to find it, press F4 to edit.
P.S. Compare to some other tools from old times, e.g. `vi`. It was wastly modernized as `vim` and still actively developed with new features added.
One of the most overlooked features is a custom user menu[1]. It allows greatly expanding MC's capabilities with custom actions and integrate it into specific workflows. No plugins or DSLs, just a `sh` calling whatever you like.
For example, I have a couple keybinds for transferring selected files/directories over rsync while browsing the remote directory over sftp. You can easily adapt it to do the same for directories mounted remotely with sshfs/rclone mount.
Another action that I like to add (this one I actually use in Double Commander on my GUI workstation) is to automatically convert transferred files on the fly, like compress media with ffmpeg (WAV to FLAC, * to OPUS, etc).
[1]: https://source.midnight-commander.org/man/mc.html#Edit_Menu_...
shmerl•4mo ago
ilvez•4mo ago
JdeBP•4mo ago
xiphias2•4mo ago
gschizas•4mo ago
machomaster•4mo ago
lepicz•4mo ago
lepicz•4mo ago
its size was right at the edge of segment (64k) so when a virus appended to the .com binary, volkov stopped working
selcuka•4mo ago
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.
tyfon•4mo ago
And MC on the *nixes of course.
auselen•4mo ago