Omarchy’s integration layer organizes upstream capabilities into desktop workflows. Omarchy Neovim configuration and Omasnap illustrate different approaches: presets for an existing editor and a user-facing screenshot application. Neither needs to call the other.
Editing configuration: a menu or terminal opens Neovim. The editor performs file editing, Omarchy’s configuration supplies workflow presets, and personal overrides express user preferences. Separating those layers avoids confusing a preset/plugin failure with a filesystem problem.
Taking a screenshot: the user invokes an Omarchy entry point, Omasnap handles the capture interaction, and the chosen action sends the result to a file or clipboard. Video recording follows a different workflow through the media-layer recording backends.
The central question is what Omarchy adds: distinguish upstream software, distribution presets, entry points and personal changes. Locate the affected layer before deciding where an update or customization belongs.
Each catalogued component is explained below: purpose, architecture, configuration, troubleshooting, limitations and further reading. Use the component links to jump to its explanation.
Provides Omarchy’s Neovim integration and presets. It makes the editor fit the distribution’s workflow while Neovim remains the editing engine.
How it works and connects
Configuration can add key mappings, plugins and appearance choices on top of the editor. Language tools may still be separate dependencies.
Configuration and customization
Read the Omarchy Neovim guide before layering a second configuration distribution. Keep personal changes separate from package-managed files.
Troubleshooting approach
Separate base-editor failures from preset or plugin failures. Record the failing feature and message instead of replacing the entire configuration first.
Limits and change considerations
Presets can change with Omarchy releases. An upstream plugin tutorial may assume a different configuration layout or plugin manager.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi omarchy-nvim
pacman -Ql omarchy-nvim
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.
Omarchy screenshot application; separate from screen recording.
Package
omasnap
Membership
Core manifest
Purpose and everyday use
Omarchy’s screenshot application for capturing a still image. Use the documented screenshot workflow when you need a region or desktop image rather than a recording.
How it works and connects
The capture target, image editing or annotation, and saving or copying are separate steps. A visible capture does not by itself confirm a file was saved.
Configuration and customization
Start from Omarchy’s documented capture shortcuts and interface. Confirm output behavior in your installed version rather than assuming paths from an older tool.
Troubleshooting approach
For a missing result, check whether the action copied instead of saved and inspect the selected destination. For wrong framing, recheck the chosen monitor or region.
Limits and change considerations
Screenshots may expose notifications, credentials or private windows. Review the image before sharing; screenshots do not replace video capture.
Local inspection and version checks
Read local package metadata to confirm installation and version. These inspection commands do not install, restart or change configuration; run them in your own Omarchy environment.
pacman -Qi omasnap
pacman -Ql omasnap
Queries can fail when a package is absent, a service is stopped, or the command needs a graphical session or project directory. Interpret the result in context. Review machine-specific details before sharing output.
Omarchy integration follows the 2026-10-12 quattro snapshot. Match upstream configuration guidance to your installed version. These are documentation-based explanations and diagnostic suggestions, not hardware-tested results.