Enhancement Proposal: Oil-Style Buffer-Based File Explorer

[emanuele-em]

Summary

The recent addition of the new file explorer, inspired by Telescope File Browser, introduces dedicated commands for managing files and directories. While this approach provides an integrated way to explore the file system, I believe a buffer-based file explorer, similar to how oil.nvim operates, would be a more natural fit for Helix’s philosophy.

Rationale

Helix emphasizes consistency in navigation and editing across different contexts. A buffer-based file explorer would allow users to interact with files and directories using the same movement commands and actions they are already familiar with, eliminating the need for dedicated file management commands or additional keybindings.

Key Advantages of a Buffer-Based File Explorer:

1. Unified Navigation & Editing: Since the file explorer is just another buffer, users can leverage Helix’s standard movement, selection, and editing commands without additional shortcuts.
2. Minimal Learning Curve: Users already proficient in Helix would find it intuitive to interact with the file system using existing workflows.
3. More Flexibility in File Management: Moving, renaming, or deleting files would feel more natural within a buffer rather than through command-specific actions.
4. Telescope pattern is not necessary: While Telescope-based approaches are excellent for fuzzy finding, such as file pickers, they are not well-suited for a file explorer. An oil-style explorer provides a more structured and flexible way to navigate directories without the need for fuzzy searching.

Proposed Behavior

• Introducing a single command, :oil, to open the current directory as a buffer.
• Display directory contents in a regular buffer where users can navigate, rename, delete, and open files as if they were text elements.
• Ensure that standard Helix motions and text objects work seamlessly within this buffer.

Addressing Potential Concerns

Some may argue that a buffer-based approach does not align with Helix’s vision. However, Helix already embraces a text-centric approach to interaction, and file exploration is fundamentally a form of structured text navigation (for example you can already open configurations with :config-open). By treating directories as editable buffers, we remain consistent with this philosophy rather than introducing a separate command paradigm, better suited for file picking and quick movements.

oil.demo.mp4