Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] CLI commands do not work #902

Open
xudyang1 opened this issue Jan 2, 2025 · 0 comments
Open

[Bug] CLI commands do not work #902

xudyang1 opened this issue Jan 2, 2025 · 0 comments
Labels
type: bug Something isn't working

Comments

@xudyang1
Copy link

xudyang1 commented Jan 2, 2025

Describe the bug

Cheatsheet commands do not work when running on CLI. They only work inside config.yaml.

Reproduction

  1. open two terminals, and run glazewm start
  2. current focus is on the left terminal, and run glazewm focus --direction right on the left terminal
  3. nothing happens.

Stack trace or error logs (if applicable)

No response

Version number

3.7.0

@xudyang1 xudyang1 added the type: bug Something isn't working label Jan 2, 2025
@github-project-automation github-project-automation bot moved this to 📬 Needs triage in glazewm Jan 2, 2025
lars-berger added a commit that referenced this issue Jan 12, 2025
* Previously, the `wm` crate contained essentially everything - it's used as a library *and* the entrypoint for both the main executable + cli. This isn't super intuitive, so it's being split out into the following:
```
wm (main app)
wm-cli (cli app)
wm-common (common types/utilities)
wm-ipc-client (small websocket client)
wm-platform (abstractions over Windows apis)
wm-watcher (watcher app)
```
* Change CLI to be a distinct binary from the `wm` crate.
  * This means the CLI can be compiled without `uiAccess`, fixing the issue where CLI commands often errors with `Permission denied` (fixes #861, #902).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
Status: 📬 Needs triage
Development

No branches or pull requests

1 participant