mq-dir vs ranger: vim philosophy meets quad-pane GUI

ranger is the file manager that vim users immediately understand. Three columns flowing left-to-right (Miller view), hjkl navigation, full vim keybindings, Python plugins. It defined an aesthetic in the 2010s.

mq-dir occupies a different design space — GUI quad-pane on macOS. They're often discussed together because both are loved by developers; they don't actually compete.

TL;DR

• ranger if you're a vim user, want Miller-column navigation, and live in terminals.
• mq-dir if you want native GUI, quad-pane parallel work, comprehensive multimedia preview.
• Run both — different parts of the daily workflow.

Side-by-side

Where ranger wins

Miller column navigation

ranger's killer feature is the three-column layout where the left shows parent dir, middle shows current dir, right shows preview. Move right (l) — what was the middle becomes the left, what was the preview becomes the middle, you go deeper. Move left (h) — reverse.

This flow is fast for hierarchical traversal. Once you get it, alternative file managers feel clunky for "drill in, glance, back out" workflows.

mq-dir doesn't have this directly. The closest equivalent is a 3-pane horizontal layout you set up manually — but it doesn't auto-flow like ranger.

Vim integration

If you live in vim/neovim, ranger sits adjacent without context-switch friction. Same hjkl, same G/gg, same : command mode. Your vim muscle memory transfers to file management for free.

mq-dir requires accepting macOS conventions. Vim users find this painful initially.

Cross-platform

ranger runs on Linux, BSD, macOS, even Windows (via WSL). mq-dir is macOS-only.

For developers who SSH between machines daily, having one file manager that works everywhere is valuable.

Plugin ecosystem

ranger's Python plugins are deep — custom previewers, custom commands, integrations with fzf, devicons, etc. The ecosystem isn't growing fast in 2026 but the existing plugins are robust.

mq-dir has no plugins yet. Roadmap mentions v0.3+.

Configuration via dotfiles

ranger's rc.conf, commands.py, colorschemes/ live in ~/.config/ranger/ and version-control nicely. Set up your config in a dotfiles repo, deploy to any machine.

mq-dir's settings are in macOS Application Support; less portable but the surface area is much smaller (mq-dir has few settings to begin with).

Where mq-dir wins

Speed on big directories

ranger is Python; on 50k+ file directories it can lag noticeably during sort or filter. mq-dir uses Swift's optimized FileManager APIs and stays smooth at any directory size we've tested (200k+ included).

Comprehensive multimedia preview

ranger's image preview requires installing chafa or w3mimgdisplay and configuring your terminal correctly. Even then, video/audio/PDF/Markdown previews are awkward.

mq-dir's preview handles images natively, plays video with controls, plays audio with waveform, renders PDF multi-page, renders Markdown with full GFM. No setup, no fragility.

Multi-pane visibility

ranger's Miller layout shows three columns of one navigation context. mq-dir's quad-pane shows four independent contexts (different folders, different projects, different sorts) simultaneously.

For multi-project / multi-AI-agent workflows, mq-dir's pattern is dramatically more useful than ranger's.

Native macOS integration

Drag from mq-dir to other apps. macOS tags read/write. Quick Look. System integrations.

ranger runs in a terminal, can't participate in macOS drag-and-drop or system features.

State persistence depth

ranger persists last directory and bookmarks. mq-dir persists everything — folder, sort, scroll, focus, hidden file toggle, column widths, preview state, projects, layouts.

The aging question

Honest assessment: ranger is the best file manager of 2014. In 2026, Yazi is faster, has better preview out-of-the-box, and is more actively maintained. ranger still works, but new users in 2026 should probably try Yazi first.

Existing ranger users with customized setups: stay until you have a reason to move. Your config investment is real.

mq-dir doesn't try to compete in the terminal space; the comparison is mostly philosophical.

Use case routing

Coexistence pattern

Same as nnn / Yazi:

• mq-dir as the GUI driver in the dock for local Mac work.
• ranger in a terminal pane for Miller-column navigation, SSH, vim-adjacent workflows.

Most heavy users settle into using each for ~50% of their file ops. No conflict; complementary roles.

What mq-dir wants to learn from ranger

1. Miller-column traversal as an option. mq-dir's 3-pane layout could auto-flow as Miller does. v0.3+ candidate.
2. Bookmark hotkeys. ranger's m<key> to bookmark and '<key> to jump is excellent. mq-dir's Favorites are sidebar-only; keyboard bookmark hotkeys would be a quick win.
3. Plugin philosophy. ranger's Python plugins are simple to write. mq-dir's eventual plugin API should match that ease.

What mq-dir won't borrow

• vim keybindings as default. macOS native conventions are the right call for the audience.
• Terminal-first design. mq-dir is GUI-first by intent.

Verdict

ranger and mq-dir solve different problems. Most heavy macOS users benefit from running both — but if you're starting from zero in 2026 and want a terminal file manager, Yazi is probably a better bet than ranger.

If you're choosing between Yazi-as-terminal and mq-dir-as-GUI, that's a different post (and the answer is also "both"). If you're choosing between ranger-only or mq-dir-only as your primary, the answer depends on whether your primary work is terminal or GUI.

mq-dir is MIT, free, no telemetry. ranger is GPL, free. Both safe long-term.