jbuchermn / newm

Wayland compositor
MIT License
960 stars 30 forks source link

Keybinding issues #107

Closed lidgnulinux closed 2 years ago

lidgnulinux commented 2 years ago

Hello, I finally able to compile newm on my debian. I'm facing a glitch or stutter (I'm not sure what's called). I have dual graphic : Intel and nvidia, the nvidia one is not active so it's just intel. Any good advice to prevent newm to glitch like this ? if it's hardware's fault then it's done. The other compositors are fine and I don't face something like this. Thanks.

[ahmad ~]$ lspci | grep VGA 00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09) 01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [GeForce GT 520M] (rev a1)

2022-05-07T10:31:41,994634919+07:00

lidgnulinux commented 2 years ago

newm log : newm_log.txt newm config : config.txt

CRAG666 commented 2 years ago

@lidgnulinux You could use my configuration and check if the problem persists, it's in my dot files(use v3 branch), obviously modify according to your preferences, also don't forget to read the tips and tricks and systemd support.

CRAG666 commented 2 years ago

I just read your configuration, it seems to me that you are still using v2, you could try using v3, in v3 many of those problems are solved. Greetings

lidgnulinux commented 2 years ago

I just read your configuration, it seems to me that you are still using v2, you could try using v3, in v3 many of those problems are solved. Greetings

Thanks @CRAG666 , I'll try it soon.

lidgnulinux commented 2 years ago

Sadly most of keybinds or shortcuts don't work, I don't know why, I try to change keyboard layout but it gives no effect.

CRAG666 commented 2 years ago

Ok, that's because I use many xf86 keys, but put the key you want, you can even use the ones you already have in v2

lidgnulinux commented 2 years ago

Yeah, I adjust it too, but still no luck.

lidgnulinux commented 2 years ago

The only working shortcuts are overview (when I press LOGO) and kill window. Dunno why. Indeed I'm no longer get glitch with configv3 configuration but can't use shortcuts is weird.

jbuchermn commented 2 years ago

Can you post the relevant config excerpts? I think there have been some recent changes

lidgnulinux commented 2 years ago

Hi, @jbuchermn , I use this config, I changed it on "output" and terminal shortcut.

jbuchermn commented 2 years ago

This uses the old format with "M-" and "ModPress". If you're on the most recent v0.3 this does not work anymore, as it has been generalized (see e.g. https://github.com/jbuchermn/newm/blob/v0.3/newm/default_config.py)

Basically instead of "M" use "S", "L", "C", "A", "1", "2" or "3" for Shift, Logo, Control, Alt, Mod1, Mod2, Mod3.

Instead of "ModPress" use "L-" e.g. if you want your Mod to be Logo.

lidgnulinux commented 2 years ago

Hi @jbuchermn , it somehow fixed, no more glitch, I just need to use default config from ~/.local/lib/(newm library path)/default_config.py, but when I move that config to ~/.config/newm it causes glitch.

jbuchermn commented 2 years ago

I'm not sure what you mean by glitch. But if you're Balte to tell which configuration options need to be set, I can add that to the documentation.

Plus: As @CRAG666 has pointed out, be sure to use v0.3

lidgnulinux commented 2 years ago

@jbuchermn , oh perhaps I need to use "stutter" term, it's like when you open window and then move it, there is artifact left.

lidgnulinux commented 2 years ago

Solved, Thanks @jbuchermn and @CRAG666.