summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
Diffstat (limited to 'README')
-rw-r--r--README32
1 files changed, 22 insertions, 10 deletions
diff --git a/README b/README
index 588a458..3a3d9bd 100644
--- a/README
+++ b/README
@@ -2,13 +2,21 @@
Modifiers:
+ Mod1- Mod1 is hard-coded as the XGrabKey modifier, which is
+ Alt on my ThinkPads. Super key has become the
+ ubiquitous WM modifier since vwm was written, but vwm
+ hasn't changed this, it's still Alt. Mostly due to
+ adding the other Alt while already pressing Alt
+ having meaning (returns focus to origin for current
+ Grab)
+
Mod1-r- Modifies some desktop/context/window switching
operations to be reversed. By itself is effectively
a noop.
Unlike the other modifiers, I haven't bothered
explicitly documenting -r's applicability below.
- It's basically: Tab, Space, and `/Grave.
+ It's basically: Tab, Space, and Grave(`).
Mod1-Shift- Modifies many operations into "Migrates". A migrate
is a focused desktop/context changing operation which
@@ -28,7 +36,12 @@ Modifiers:
migrate, no actual switching occurs.
These also haven't been explicitly documented below,
- currently it's basically: `/Grave, and 0-9.
+ currently it's basically: Grave(`), and 0-9.
+
+ Mod1-m- Modifies window configuring / focus-changing events to
+ behave in a mouse-follows-focus manner. Composes with
+ the above as well, and may be used independently to simply
+ center the pointer in the currently focused window.
Built-in operations:
@@ -156,9 +169,8 @@ Built-in operations:
multihead configurations the next window selection is
further confined to within the current screen+desktop.
- Mod1-Shift-Tab Identical to Mod1-Tab except switches to the MRU
- window on another screen in a multihead
- configuration.
+ Mod1-\ Identical to Mod1-Tab except switches to the MRU
+ window on another screen in a multihead configuration.
Mod1-d Request the client destroy the focused window, or
destroy the current virtual desktop when no windows
@@ -225,11 +237,11 @@ Built-in operations:
Default launchers (configure by editing launchers.def and rebuild):
Mod1-x xterm
- Mod1-b iceweasel
- Mod1-g gimp
Mod1-. xlock
Mod1-- xset -dpms s off
Mod1-= xset +dpms s on
+ Mod1-BackSpace recordmydesktop --windowid %W
+ Mod1-Delete recordmydesktop
General:
@@ -358,7 +370,7 @@ Composite/Monitoring:
Here are some relevant things worth noting:
- - The monitoring is only heirarchical if your kernel is configured with
+ - The monitoring is only hierarchical if your kernel is configured with
CONFIG_CHECKPOINT_RESTORE, which seems to be common nowadays. This is
required for the /proc/$pid/task/$tid/children files, which is what
libvmon uses to efficiently scope monitoring to just the descendants of
@@ -459,7 +471,7 @@ Composite/Monitoring:
exacerbate the situation.
- The monitoring is implemented using sampling, not tracing. Below the
- current process heirarchy for every window there is an exited tasks
+ current process hierarchy for every window there is an exited tasks
snowflakes section filling the remaining space. Do not mistake this
for something lossless like bash history or strace output, it's lossy
since it's produced from sampled data. In part to try avoid
@@ -495,7 +507,7 @@ Composite/Monitoring:
- In the interests of being efficient, nothing is being logged
historically. The snowflakes area is all you get, which is limited to
- the free pixel space below the instantaneous process heirarchy within
+ the free pixel space below the instantaneous process hierarchy within
the window.
Everything which falls off the edges of the screen is lost forever,
© All Rights Reserved