A Neovim file manager that lets you edit the file system like a buffer with a tree view.
Fyler.nvim is a file manager plugin for Neovim that integrates directly into the editor, providing a tree view interface for browsing directories and files. It allows users to manage files and directories as if they were buffers, enabling seamless navigation and editing within the Neovim environment without switching to external tools.
Neovim users who want an integrated, native-feeling file management solution directly within their editor, particularly those who prefer to avoid external file explorers or terminal commands.
Developers choose Fyler.nvim for its deep integration with Neovim's buffer system, allowing file operations to feel like editing text buffers, and for its flexible window layouts that adapt to various workflow preferences within the editor.
A neovim file manager which can edit file system like a buffer with tree view
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Files are managed as if they were text buffers, enabling intuitive editing and navigation within Neovim's workflow, as emphasized in the philosophy for a seamless experience.
Supports various window kinds like splits or dedicated panes, allowing users to adapt the file manager to their preferred layout, detailed in usage examples with options such as 'split_left_most'.
Provides a Lua API for personalized key mappings and actions, enabling developers to tailor file management to their workflow, as shown in the usage section with vim.keymap.set examples.
Offers both stable and latest branches with clear installation instructions, including lazy loading support, making it accessible for different user preferences, as outlined in the README.
Requires 'nvim-mini/mini.icons' as a dependency, adding complexity to setup and potential conflicts with other icon plugins in a user's configuration.
Focuses on simplicity, which may mean it lacks advanced file operations like bulk edits, deep search integration, or performance optimizations for very large directories, compared to more comprehensive alternatives.
The README directs users to run ':help fyler.nvim' or visit wiki pages for detailed explanations, indicating that in-editor help might be sparse, requiring additional steps for full understanding.