Feature proposal: More sophisticated per-workspace normalizations to replicate dynamic twm

AeroSpace already provides two normalizations ("flatten-containers" and "opposite-orientation-for-nested-containers") The current mental model of normalizations can be extended to allow more types of normalizations. To completely replicate dynamic tiling window managers, it should be possible to change normalizations with command on per-workspace basis Normalizations to consider: - `floating`. All windows on the workspace are floating. Open question: should the normalization remember and restore layout from the workspace where this normalization wasn't enabled? - `columns` - `rows` - `primary-others` ("tall" in Amethyst) - `others-primary` ("tall-right" in Amethyst) - `v-primary-others` ("wide" in Amethyst) - `v-others-primary` - `bsp` To consider: file with declarative hierarchical normalization description (something like yaml, but probably not yaml) It should also be possible to apply the normalization once, but don't keep it persistent Related: #228 #248 #256 Related: - https://github.com/eliep/i3-layouts/tree/main

Posted by nikitabobko on Jun 8, 2024, 2:56 PM

Tags

• github (Software)

Related issues

• [Meta] Feedback on granular control over Copilot changes
• unexpected status 401 Unauthorized issue
• [MODEL] Measurable quality regression in Claude generation 5 (Fable 5 / Opus 5 / Sonnet 5): worse nonsense detection, ~2x verbosity, under-disclosed model fallb
• [CRITICAL] Subagent spawning and subagent pattern bugs trigger infinite recursion, infinite token usage, grossly inefficient token usage, and lost accumulated s
• Video stops playing after some minutes
• [MODEL] Claude verbose code comments by default — ignores instructions to stop.