'\" t
.\"     Title: picom-inspect
.\"    Author: Yuxuan Shui
.\" Generator: Asciidoctor 2.0.26
.\"      Date: 2026-04-03
.\"    Manual: User Commands
.\"    Source: picom-inspect
.\"  Language: English
.\"
.TH "PICOM\-INSPECT" "1" "2026-04-03" "picom\-inspect" "User Commands"
.ie \n(.g .ds Aq \(aq
.el       .ds Aq '
.ss \n[.ss] 0
.nh
.ad l
.de URL
\fI\\$2\fP <\\$1>\\$3
..
.als MTO URL
.if \n[.g] \{\
.  mso www.tmac
.  am URL
.    ad l
.  .
.  am MTO
.    ad l
.  .
.  LINKSTYLE blue R < >
.\}
.SH "NAME"
picom-inspect \- easily test your picom rules
.SH "SYNOPSIS"
.sp
\fBpicom\-inspect\fP [\fIOPTIONS\fP]
.SH "DESCRIPTION"
.sp
\fBpicom\-inspect\fP matches your picom rules against a window of your choosing. It helps you test your rules, and shows you which ones of your rules (don\(cqt) work.
.SH "OPTIONS"
.sp
\fBpicom\-inspect\fP accepts all options that \fBpicom\fP does. Naturally, most of those options will not be relevant.
.sp
These are some of the options you might find useful (See \fBpicom\fP(1) for descriptions of what they do):
.sp
\fB\-\-config\fP, \fB\-\-log\-level\fP, \fB\-\-log\-file\fP, all the options related to rules.
.sp
\fBpicom\-inspect\fP also accepts some extra options:
.RS 4
.sp
\fB\-\-monitor\fP
.RS 4
Keep \fBpicom\-inspect\fP running in a loop, and dump information every time something changed about a window.
.RE
.RE
.SH "NOTES"
.sp
\fBpicom\-inspect\fP is prototype right now. If you find any bug, for example, if rules are matched differently compared to \fBpicom\fP, please submit bug reports to:
.sp
.URL "https://github.com/yshui/picom" "" ""
.SH "RESOURCES"
.sp
Homepage: \c
.URL "https://github.com/yshui/picom" "" ""
.SH "SEE ALSO"
.sp
\fBxcompmgr\fP(1), \fBpicom\fP(1)
.SH "AUTHOR"
.sp
Yuxuan Shui