mirror of
https://github.com/wavetermdev/waveterm
synced 2026-04-21 14:37:16 +00:00
## Summary
This PR adds vim-style movement aliases for block navigation and updates
one conflicting
shortcut.
## Changes
- Added global keybindings:
- `Ctrl+Shift+h` -> move focus left
- `Ctrl+Shift+j` -> move focus down
- `Ctrl+Shift+k` -> move focus up
- `Ctrl+Shift+l` -> move focus right
- Kept existing arrow-based movement:
- `Ctrl+Shift+ArrowUp/Down/Left/Right`
- **Changed launcher shortcut**:
- from `Ctrl+Shift+k`
- to `Ctrl+Shift+x`
## Why `k` changed to `x`
`Ctrl+Shift+k` is now used for vim-style upward movement (`k` = up), so
launcher replace
needed a new binding.
`Ctrl+Shift+x` was chosen to avoid collisions with existing Wave global
keybindings.
## Config / behavior notes
- `app:disablectrlshiftarrows` now disables both block-navigation sets:
- Arrow keys
- `h/j/k/l` aliases
- It does **not** disable `Ctrl+Shift+x` (launcher replace).
## Docs updated
- `docs/docs/keybindings.mdx`
- Added `Ctrl+Shift+h/j/k/l` navigation display
- Updated launcher replace shortcut to `Ctrl+Shift+x`
- `docs/docs/config.mdx`
- Clarified `app:disablectrlshiftarrows` scope to include `Arrow` +
`h/j/k/l`
|
||
|---|---|---|
| .. | ||
| docs | ||
| src | ||
| static | ||
| .editorconfig | ||
| .gitignore | ||
| .prettierignore | ||
| .remarkrc | ||
| babel.config.js | ||
| docusaurus.config.ts | ||
| eslint.config.js | ||
| package.json | ||
| prettier.config.cjs | ||
| README.md | ||
| tsconfig.json | ||
Wave Terminal Documentation
This is the home for Wave Terminal's documentation site. This README is specifically about building and contributing to the docs site. If you are looking for the actual hosted docs, go here -- https://docs.waveterm.dev
Installation
Our docs are built using Docusaurus, a modern static website generator.
Local Development
task docsite
This command starts a local development server and opens up a browser window. Most changes are reflected live without having to restart the server.
Build
task docsite:build:public
This command generates static content into the build directory and can be served using any static contents hosting service.
Deployment
Deployments are handled automatically by the Docsite CI/CD workflow