xcompose
Simple utilities to help configure X11 compose key sequences.
The repo also hosts a very extensive .XCompose file with over 42 000 new sequences; more details here.
Installation
$ pip install xcompose
Requirements
Currently assumes that the system compose key configurations are in /usr/share/X11/locale/, while the keysym definitions are in /usr/include/X11/keysymdef.h.
Only tested on Ubuntu 24, but should work more widely (though still very much beta quality).
Usage
$ xcompose -h
usage: xcompose [-h] [-f FILE | -S] [-i] [-k KEY] [-s SORT] {add,find,get,validate} ...
XCompose sequence helper utility.
positional arguments:
{add,find,get,validate}
add print a new compose sequence
find find sequences matching given output
get get sequences matching given key inputs
validate validate compose config file
options:
-h, --help show this help message and exit
-f FILE, --file FILE config file to analyze (instead of user config)
-S, --system analyze system config (instead of user config)
-i, --ignore-include don't follow any include declarations in the config
-k KEY, --key KEY modifier key keysym (default is Multi_key; use ANY for all)
-s SORT, --sort SORT sort resulting sequences (options: 'keys', 'value')
Examples
$ xcompose find é
<Multi_key> <acute> <e> : "é" eacute # LATIN SMALL LETTER E WITH ACUTE
<Multi_key> <e> <acute> : "é" eacute # LATIN SMALL LETTER E WITH ACUTE
<Multi_key> <apostrophe> <e> : "é" eacute # LATIN SMALL LETTER E WITH ACUTE
<Multi_key> <e> <apostrophe> : "é" eacute # LATIN SMALL LETTER E WITH ACUTE
$ xcompose find pound
<Multi_key> <L> <minus> : "£" sterling # POUND SIGN
<Multi_key> <minus> <L> : "£" sterling # POUND SIGN
<Multi_key> <l> <minus> : "£" sterling # POUND SIGN
<Multi_key> <minus> <l> : "£" sterling # POUND SIGN
$ xcompose find U+00B5
<Multi_key> <m> <u> : "µ" mu # MICRO SIGN
<Multi_key> <slash> <u> : "µ" mu # MICRO SIGN
<Multi_key> <u> <slash> : "µ" mu # MICRO SIGN
$ xcompose get / =
<Multi_key> <slash> <equal> : "≠" U2260 # NOT EQUAL TO
$ xcompose --sort keys get /
<Multi_key> <slash> <minus> : "⌿" U233f # / - APL FUNCTIONAL SYMBOL SLASH BAR
<Multi_key> <slash> <slash> : "\\" backslash # REVERSE SOLIDUS
<Multi_key> <slash> <less> : "\\" backslash # REVERSE SOLIDUS
<Multi_key> <slash> <equal> : "≠" U2260 # NOT EQUAL TO
<Multi_key> <slash> <B> : "Ƀ" U0243 # LATIN CAPITAL LETTER B WITH STROKE
<Multi_key> <slash> <C> : "₡" U20a1 # COLON SIGN
<Multi_key> <slash> <D> : "Đ" Dstroke # LATIN CAPITAL LETTER D WITH STROKE
⋮
<Multi_key> <slash> <U2194> : "↮" U21AE # LEFT RIGHT ARROW WITH STROKE
<Multi_key> <slash> <U2395> : "⍁" U2341 # / ⎕ APL FUNCTIONAL SYMBOL QUAD SLASH
$ xcompose add ɕ c @
<Multi_key> <c> <at> : "ɕ" U0255 # LATIN SMALL LETTER C WITH CURL
$ xcompose add ć c /
<Multi_key> <c> <slash> : "ć" U0107 # LATIN SMALL LETTER C WITH ACUTE (conflicts with ¢)
$ echo '<Multi_key> <c> <comma> <quote> : "ḉ"' >> ~/.XCompose # add a line to .XCompose
$ xcompose validate
[/home/Udzu/.XCompose#116] Unrecognised keysym: quote
[/home/Udzu/.XCompose#116] Missing keysym: expected U1E09
[/home/Udzu/.XCompose#116] Missing comment: expected LATIN SMALL LETTER C WITH CEDILLA AND ACUTE
[/home/Udzu/.XCompose#116] Compose sequence Multi_key + c + comma + quote for 'ḉ' conflicts with
[/usr/share/X11/locale/en_US.UTF-8/Compose#428] Multi_key + c + comma for 'ç'
to ignore this, include the string 'conflict' or 'override' in the comment
$ xcompose -S validate # system config isn't validated by default (only parsed for conflicts)
[/usr/share/X11/locale/en_US.UTF-8/Compose#73] Incorrect comment: LESS-THAN, expected LESS-THAN SIGN
[/usr/share/X11/locale/en_US.UTF-8/Compose#74] Incorrect comment: LESS-THAN, expected LESS-THAN SIGN
[/usr/share/X11/locale/en_US.UTF-8/Compose#75] Incorrect comment: GREATER-THAN, expected GREATER-THAN SIGN
[/usr/share/X11/locale/en_US.UTF-8/Compose#76] Incorrect comment: GREATER-THAN, expected GREATER-THAN SIGN
[/usr/share/X11/locale/en_US.UTF-8/Compose#121] Incorrect keysym: guillemotleft, expected guillemetleft (or U00AB)
[/usr/share/X11/locale/en_US.UTF-8/Compose#122] Incorrect keysym: guillemotright, expected guillemetright (or U00BB)
[/usr/share/X11/locale/en_US.UTF-8/Compose#198] Incorrect comment: ROUBLE SIGN, expected RUBLE SIGN
⋮
[/usr/share/X11/locale/en_US.UTF-8/Compose#253] Incorrect keysym: masculine, expected ordmasculine (or U00BA)
[/usr/share/X11/locale/en_US.UTF-8/Compose#4985] Incorrect comment: ○ \ APL FUNCTIONAL SYMBOL CIRCLE SLOPE, expected APL FUNCTIONAL SYMBOL CIRCLE BACKSLASH
[/usr/share/X11/locale/en_US.UTF-8/Compose#4986] Incorrect comment: \ ○ APL FUNCTIONAL SYMBOL CIRCLE SLOPE, expected APL FUNCTIONAL SYMBOL CIRCLE BACKSLASH
Formatting
There is also a separate utility for helping format configs so that definitions line up nicely.
$ xcfmt -h
usage: xcfmt [-h] [-o FILE] [-k N] [-v N] [FILE]
XCompose config formating utility.
positional arguments:
FILE file to format (uses stdin if unspecified)
options:
-h, --help show this help message and exit
-o FILE, --output FILE
file to write output to (uses stdout if unspecified)
-k N, --max-key-indent N
maximum indentation up to the colon (default: 40)
-v N, --max-value-indent N
maximum indentation up to the comment (default: 10)
Metadata
Release files for xcompose 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| xcompose-0.5.1.tar.gz | 641.4 kB | With provenance | Details for xcompose-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| xcompose-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for xcompose-0.5.1-py3-none-any.whl |
Total release size: 683.6 kB
Release files / xcompose-0.5.1.tar.gz
| Download URL | xcompose-0.5.1.tar.gz |
|---|---|
| Size | 641.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
7ea3a89ad6063de2293dbbb18cd60847c01517aac54ac9a1f7d28f1062d061de
|
|
BLAKE2b-256 checksum How to use checksums |
d4b58b585f61c25c52f056f358ce0dae2d04033f5915890ff7cac0699ca326a3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2025.
Transparency logRelease files / xcompose-0.5.1-py3-none-any.whl
| Download URL | xcompose-0.5.1-py3-none-any.whl |
|---|---|
| Size | 42.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6982d5f47675ff8069ef07343bdb5e30a4d6f9f4d969e538bb352df445af0bde
|
|
BLAKE2b-256 checksum How to use checksums |
214d5f870ce3c0a971d470066498044dcfccb4dea810ce6fa0caac428707a986
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2025.
Transparency logSecurity for xcompose 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for xcompose-0.5.1.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jul 17, 2025.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.