# 9. Files, editing, and media Alloy ships one default per job. All of them are keyboard-driven, and most of them are vim-shaped. ## Files: yazi yazi A two-pane file manager in the terminal, with previews. Under shop it renders images inline using the kitty graphics protocol rather than falling back to coloured blocks, which is most of what the terminal is asked for here. `?` lists its keys. `q` leaves. There is no graphical file manager in the image. Apps that need to open or save a file get a portal dialog, which is what a browser uses, so the daily case is covered. If you want one anyway, it comes from a flatpak remote you add (chapter 7). ## Editing: helix hx Modal, selection-first: you select and then act, so it is `3wd` where vim is `d3w`. Language servers, tree-sitter highlighting, and formatters are built in rather than assembled from plugins. It is useful with no configuration. `EDITOR` is set to `hx`, so git commit messages and everything else that respects `$EDITOR` open here. Alloy ships the Akari theme and a small config at `~/.config/helix/`. If you have vim muscle memory, expect a week or two of friction; the grammar is a real improvement but it is not the one your fingers know. `:tutor` is the fastest way through. ## PDFs: zathura zathura vim keys, statusbar-only chrome. `i` toggles recolouring, which is off in the day theme (the page already agrees with the chrome) and on at night (an unrecoloured PDF in a dark session is a floodlight). zathura reads. It does not annotate, and Alloy does not ship an annotator. ## Images: imv imv Wayland-native, tiny, vi-like keys. The overlay is hidden until you ask for it. ## Video and audio: mpv mpv No chrome by default, hardware decoding on, screenshots to `~/Pictures/Screenshots`. It plays streams through yt-dlp, capped at 1080p in the shipped config. A fullscreen mpv window holds the screen lock off. A windowed one does not, because a windowed video is usually something being glanced at. ## System monitoring: bottom btm or `top`, which is aliased to it. ratatui-based, same visual family as the console. Clicking is disabled on purpose; it is keyboard-only. ## Disk usage: dua du is aliased to `dua interactive`. Navigate with vim keys, mark things for deletion, delete them. ## Clipboard history Everything you copy is recorded, text and images both. `Mod+Shift+V` opens a picker over the history; choose an entry and it goes back on the clipboard. The store is at `~/.local/share/cliphist/db` and needs no configuration. If you want a copy to never be recorded, there is no per-copy exclusion today; clear the history with `cliphist wipe`. ## Screenshots and annotation Covered in chapter 5. The one thing worth repeating here: `Mod+Print` opens the most recent capture in satty, which is where you crop, arrow, and blur before sending it somewhere. ## The browser Firefox ships in the image as the default browser. It comes from Fedora's own repositories, which matters more than it sounds: those stay enabled after you install, so a machine built with no browser at all is one `rpm-ostree install firefox` away from this one. Alloy changes exactly one file, `/etc/firefox/pref/alloy.js`, and it is worth knowing what is in it because the rule it follows is short. Alloy turns off things that serve somebody other than you: telemetry, sponsored placements on the new tab page and in the address bar, and the AI features, which arrive switched on and download models nobody asked for. It sets tracking protection to strict. It also turns on one thing, `browser.compactmode.show`, which puts the density control back in Customize where Mozilla hides it. That last one is the pattern rather than an exception. Alloy would rather hand you back a control than pick the value for you, so it does not set the density itself: compact is one click away in Customize and the choice stays yours. Nothing in that file is locked. Every line is a starting position you can change in Settings, and if you disagree with all of it, changing all of it is supported. There is no policy file, no autoconfig, and no chrome CSS. Anything past what a well-behaved app reads from the system (light or dark, the GTK theme for dialogs, the cursor, the fonts) is yours to set in the browser's own settings. Two honest notes. Because the browser lives in the image, it updates when you rebuild the image and not before (chapter 8). And Mozilla renames preferences between releases, so a line in that file can quietly stop applying; the file records which Firefox version its names were read from.