aboutsummaryrefslogtreecommitdiff
path: root/keymaps.h
Commit message (Collapse)AuthorAge
* use ModLayer keys instead of custom macrodakkar2022-10-07
|
* now it compilesdakkar2022-09-23
|
* fvwm "num" is "screenshot"dakkar2021-02-28
|
* kill numpaddakkar2021-02-28
| | | | I only ever hit it by accident
* use alt+f10 to bring up the mixerdakkar2019-11-21
|
* alt + layer shiftdakkar2019-11-21
|
* put raise/lower window on pgup/dn, close window farther awaydakkar2019-11-21
|
* add raise/lawer fvwm keysdakkar2019-07-30
|
* move insert to thumb arcdakkar2019-07-22
|
* numlock as a macrodakkar2019-02-22
| | | | | | | | | | Press the NumLock key, switch the layer. Previously, pressing the NumLock key was handled by the NumPad plugin (which mostly deals with LED colors). I stopped using that plugin when I built my own LED plugin. Also, recently the NumPad plugin stopped handling the NumLock press, so we really need to do it here.
* kill capslockdakkar2019-02-21
|
* fix numpaddakkar2019-02-21
|
* use new keyclassesdakkar2019-02-21
|
* mare everything as C++ for EMACSdakkar2019-02-10
|
* move color themes to their own filedakkar2019-02-10
|
* mixed static / functional colorsdakkar2019-02-10
| | | | this probably replaces the Numpad plugin completely
* more flexible / simpler color specificationdakkar2019-02-10
|
* keep NumLock working in all layersdakkar2019-02-09
| | | | otherwise there's no way to get *out* of the numlock layer
* maybe working color maps?dakkar2019-02-09