Skip to content

welcome to rovr

normal user interface

let’s use the 5W1H framework to describe rovr and its latest improvements

a modern answer to a terminal file explorer, that can be customized to fit your workflow easily, while being aesthetically pleasing. rovr now features advanced state management, flexible compact modes, and an improved sort order switcher for enhanced usability.

rovr now includes a comprehensive state management system that automatically saves and restores your preferences:

  • panel visibility settings persist between sessions
  • sort criteria and direction preferences are remembered
  • seamless integration with compact mode settings
  • automatic version tracking for compatibility

the new sort order switcher provides quick access to sorting options:

  • cycle through different sort orders without opening menus
  • visual feedback with icons showing current sort type and direction
  • all sort preferences are automatically saved via the state manager

compact mode has been expanded into granular options:

  • header compact mode: reduces header height for more vertical space
  • footer compact mode: auto-hides footer panels when not in use
  • legacy compact mode: maintains backward compatibility
  • state manager preserves your manual panel preferences even in compact modes

I can’t answer this question, but I can answer why you shouldn’t use rovr.
you shouldn’t use rovr if

  1. you have an existing workflow with any other file explorers (superfile excluded)
    other file managers like yazi, ranger or nnn are amazing file explorers, and rovr cannot compete with their flexibility, extensibility or just raw speed.

  2. when you are allergic to non-compiled apps
    rovr is made in python, and uses some features that prevents it from being compiled by pyinstaller or nuitka. if you are someone who is allergic to such an app, please step away now.

I had quite some issues with superfile. it is an amazing project, and you should definitely go check it out.


however, some issues I had was with its performance. spf does not utilize either threads nor asyncio, everything runs on a single app process, which can lead to plenty of lag when traveling.
I wouldve loved to fix these issues, but I dont have any golang background, and I found textual as a framework, and really wanted to put my skills to the test.
so I guess we are here now.