Commit 62e7e56

docs: readme

 1@@ -290,25 +290,6 @@ zmx k tests  # kills d.tests
 2 zmx wait     # suspends until all tasks prefixed with "d." are complete
 3 ```
 4 
 5-## label inheritance
 6-
 7-When creating a new session from inside an existing one (`$ZMX_SESSION` is set), labels are automatically inherited from the parent session. This means if you set `project=zmx` on a session, any child sessions created from within it will also have `project=zmx`.
 8-
 9-To control which labels are inherited, set `ZMX_INHERIT_LABELS`:
10-
11-```bash
12-# Inherit all labels (default)
13-zmx a child
14-
15-# Inherit no labels
16-export ZMX_INHERIT_LABELS=
17-zmx a child
18-
19-# Inherit only specific labels
20-export ZMX_INHERIT_LABELS=project,team
21-zmx a child
22-```
23-
24 ## philosophy
25 
26 The entire argument for `zmx` instead of something like `tmux` that has windows, panes, splits, etc. is that job should be handled by your os window manager. By using something like `tmux` you now have redundant functionality in your dev stack: a window manager for your os and a window manager for your terminal. Further, in order to use modern terminal features, your terminal emulator **and** `tmux` need to have support for them. This holds back the terminal enthusiast community and feature development.