glacambre/firenvim
Firenvim
Firenvim is a browser integration and plugin that replaces web text areas and input fields with a full Neovim editor instance. It acts as a web-based text editor that synchronizes Neovim buffers with browser DOM elements to enable advanced text manipulation and web content authoring.
The system utilizes a bidirectional buffer synchronizer to automatically update browser input fields as the editor buffer is modified. It includes a browser DOM manipulator for executing JavaScript expressions and simulating keyboard events on web pages directly from the editor environment. For security, an external process sandbox isolates the editor instance from the host operating system.
The project covers contextual configuration management, allowing editor settings and filename generation to be determined by URLs, domains, or CSS selectors. It also provides control over element takeover triggers, keystroke filtering for native browser shortcuts, and options to handle content as either plain text or raw HTML.
Features
- Browser-to-Editor Synchronization - Acts as the primary communication bridge for real-time mirroring of text between web input fields and an external editor.
- Browser-Embedded Editors - Injects a full-featured Neovim editing interface into web input fields to replace basic text area capabilities.
- Web Authoring Interfaces - Allows using a full Neovim instance to author and refine long-form content directly within browser text areas.
- Neovim Plugins - Provides a browser extension and plugin that integrates Neovim as a replacement for web text areas.
- DOM-Based Text Manipulations - Modifies the browser DOM by synchronizing external Neovim buffers with web input elements.
- Neovim-Based Editors - Implements an editing interface that uses Neovim as the core engine for manipulating web-based text content.
- Buffer State Synchronization - Implements real-time synchronization of text buffers between the Neovim editor and browser input fields.
- Inter-Process Message Passing - Provides a communication bridge for exchanging state and commands between the browser extension and the external editor process.
- Content Editable Proxies - Replaces browser input fields with a hidden content-editable proxy to capture keystrokes and synchronize state.
- Input Takeover Mechanisms - Replaces standard browser text areas with hidden editable elements to capture keystrokes and trigger the editor.
- Text Editing Components - Replaces standard browser text areas and input fields with a high-performance text editor component.
- Content Exchange Formats - Allows configuring whether content is synchronized between the editor and web elements as plain text or raw HTML.
- Browser-Based Workflows - Enables the execution of JavaScript and keyboard event simulation on web pages directly from the editor.
- URL-Based Behavioral Configuration - Adjusts editor behavior and settings automatically based on the current domain, URL, or HTML element.
- Editor Sandboxes - Isolates the Neovim editor process from the host operating system using security profiles to restrict system access.
- Process Sandboxing - Uses security profiles to isolate the external editor process from the host operating system.
- Takeover Element Selection - Defines which HTML elements are replaced by the editor using CSS selectors and replacement triggers.
- Takeover Trigger Controls - Controls whether text fields are replaced automatically, only when empty, or via manual keyboard shortcuts.
- Element Target Resolution - Uses CSS selectors and URL patterns to identify specific HTML elements to be replaced by the editor.
- DOM Manipulators - Provides tools to programmatically execute scripts and simulate events to modify the browser's document object model.
- Activation Triggers - Determines when the editor interface activates based on element state, CSS selectors, and URLs.
- HTML Content Management - Provides the ability to fetch and modify the content of web elements specifically as raw HTML.
Star history
How this analysis was created: This summary and feature list were written by an AI model that read the project's README and public documentation pages. Each feature links to the documentation it came from; stars, license and language come straight from the GitHub API. The model does not read the source code, and the analysis is refreshed when the project is re-analysed. Learn more on our About page.
