Crates.io | miro-pdf |
lib.rs | miro-pdf |
version | 0.6.1 |
created_at | 2025-05-07 14:05:31.12417+00 |
updated_at | 2025-09-05 12:04:29.398481+00 |
description | A native pdf viewer for Windows and Linux (Wayland/X11) with configurable keybindings. |
homepage | https://vincentuden.xyz |
repository | https://github.com/vincent-uden/miro |
max_upload_size | |
id | 1663891 |
size | 1,613,881 |
A native pdf viewer for Windows and Linux (Wayland/X11) with configurable keybindings.
The configuration file is located at ~/.config/miro-pdf/miro.conf
(or .config/miro-pdf/miro.conf
in the home directory of your operating system). An example configuration file is located at /assets/default.conf
which contains all the default bindings for the program.
The configuration file uses a simple text format with three types of commands:
# This is a comment
# Comments start with # and are ignored during parsing
# Empty lines are also ignored
Bind <key_sequence> <action>
Key sequences can be:
j
, k
, h
, l
Ctrl+r
, Shift+Tab
"Z Z"
(quotes required for sequences with spaces)All available actions are bound in the example config file.
MouseBind <mouse_input> <action>
Mouse inputs can be:
MouseLeft
, MouseRight
, MouseMiddle
, MouseBack
, MouseForward
Ctrl+MouseLeft
, Shift+MouseRight
All available actions are bound in the example config file.
Set <setting> <value>
Available settings:
Rpc <True|False>
- Enable/disable RPC serverRpcPort <number>
- Set RPC server portThe configuration parser provides detailed error messages with line numbers when parsing fails. Errors on one line don't prevent parsing of other lines
Example error output:
Configuration parsing errors:
Line 3: Unknown command: InvalidCommand
Line 5: Unknown action: InvalidAction
Line 7: Invalid port number: 'not_a_number'. Must be a valid integer
Head over to releases and download the latest binary for your platform, then place it somewhere in your path.
This is pretty much the same as the following option, but doesn't require cloning the repo. See building from source for possible complications when compiling for Windows. I've had no problems compiling on Linux thus far.
cargo install miro-pdf
On linux, the commands below would clone the repository, compile the project and copy the resulting binary to /usr/bin/
.
git clone https://github.com/vincent-uden/miro.git
cd miro
cargo r --release
cp ./target/release/miro /usr/bin/miro
On Windows, the same rough process should work, but often doesn't. I highly recommend downloading a precompiled binary for Windows. The problem lies in compiling the crate mupdf-sys
which requires MSVC.
The Visual Studio project embedded in this crate requires Visual Studio 2019 which isn't available for downloading anymore, but can optionally be compiled using Visual Studio 2022. Even with this option, the build might just not work sometimes due to issues with the Windows 10/11 SDK kits which I have not managed to solve.
However, I've managed to get compilation working in github actions which is what produces the release binaries which do function correctly on Windows systems.
Building on linx require some hidden dependendencies that you probably already have. On arch they are:
clang
unzip