Re: [dev] [dwm] Question regarding `unmanage()` in while loop

2016-08-04 Thread Alexander Monakov
On Wed, 3 Aug 2016, Paul Menzel wrote: > dwm.c:480:4: warning: Use of memory after it is freed > unmanage(m->stack, 0); > ^ I think the warning is correct: after m->stack is free'd in unmanage, the subsequent 'focus(NULL)' call i

Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
On Sat, 16 Jul 2016, FRIGN wrote: > nice work soldier! Can you elaborate on how you measured the syscalls > per second? I simply invoked strace in the following fashion (bash): $ sleep 1; strace -cfp `pidof dwm` & sleep 1; kill % (this wouldn't be accurate at very high syscall rates due to s

Re: [dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
On Sat, 16 Jul 2016, Staven wrote: > On Sat, Jul 16, 2016 at 02:33:18PM +0300, Alexander Monakov wrote: > > This causes lots of useless communication between the X server and dwm every > > time the mouse pointer is moved, even when nothing could possibly change as > > a result

[dev] [dwm] Avoid requesting MotionNotify events

2016-07-16 Thread Alexander Monakov
Hi, A while ago dwm started requesting MotionNotify events from the X server (that wasn't always the case). This was added when focus-follows-mouse was implemented for monitors (in addition to windows) in 2011 by commit b5068e32e9. This causes lots of useless communication between the X server an