VuiMuich
VuiMuich
Well very basic command execution would be like this I guess: ```rust std::process::Command::new("leftwm-check".to_string()).args("--panic".to_string()).spawn()?; ```
Oopsie forgot about the terminal part. Idk if it's related, but doesn't Alacritty have a flag to make the window persistent after the commend finished?
I did a fresh build with the latest merges of today and get: ``` >>> target/release/leftwm-check :: LeftWM version: 0.4.2 :: LeftWM git hash: 0.4.2-20-gc4a734c :: Enabled features: journald-log lefthk...
There is two things: the `""` in the empty modifiers don't work because "empty string" does not serialize corect and the "media keys" don't match with the [keysyms ](https://github.com/leftwm/lefthk/blob/main/lefthk-core/src/xkeysym_lookup.rs#L50). This...
Sorry, I skipped that part.. Those seem to be actual bugs, I can reproduce them our new nixos dev vm.. Thanks for reporting!
I tried it as external commands in the VM, which reported command execution but nothing happened.
Still I think the external commands might be broken, so I keep this open for now.
Probably won't have time before Thursday.
Correct me if I am wrong, but as far as I understood wayland last time I dug into this topic, lots of the functionality that in X11 the WM handles...
> Am I correct that leftwm is architected to allow implementation of other backends via implementing the `display_server` traits for that backend? Are there other places where X11 specific code...