kragen / xcompose
- Source
- Commits
- Network (1)
- Issues (0)
- Downloads (0)
- Wiki (1)
- Graphs
-
Tree:
8f50009
commit 8f50009cb0529e32f5dcc4051c3a5ab92a1e6bad
tree d3bb54954122cf234d62c4166a517d47d3fae098
parent a62fcb5659aa793ff06fac05e8be4f190d2a9cac
tree d3bb54954122cf234d62c4166a517d47d3fae098
parent a62fcb5659aa793ff06fac05e8be4f190d2a9cac
xcompose /
| name | age | message | |
|---|---|---|---|
| |
.gitignore | ||
| |
README.md | ||
| |
dotXCompose | ||
| |
install | ||
| |
scan4dups.py |
README.md
.XCompose
As explained in http://canonical.org/~kragen/setting-up-keyboard.html,
your Compose key in X11 is controlled by (among other things) the file
.XCompose in your home directory. This file gives you a large set
of bindings for Unicode characters that are useful occasionally.
More contributions are welcome; there's a Git repository at http://github.org/kragen/xcompose. We're trying to come up with a broadly acceptable set of keybindings that won't interfere with the traditional Compose bindings, aren't too hard to type, and cover a wide set of characters that are useful to use occasionally, making them available without the need for specialized input methods.

