On 2016-04-12 at 11:09, Marc Collin wrote:
> Really a bug or something wrong only for me?
I haven't noticed until now, but I can reproduce the problem with
static char font[] = "Inconsolata for
Powerline:pixelsize=16:antialias=false:autohint=false";
Best regards,
Andreas
Hello
I've noticed that after applying the argbbg patch to st, the window borders
become transparent as well. This only happens with patched st, not with other
applications (tested with xterm, urxvt, gnome-terminal and zathura), so I
think the behaviour arises from the patch.
See an example [1] w
On 2016-01-15 at 23:21, Markus Teich wrote:
> I don't like the man-page approach. Documentation always looses
> synchronization
> to the codebase, so my proposal would be to output a similar error message in
> slock. The link from "slock: could not grab pointer" to `unclutter -grab`
> should
> be
On 2016-01-15 at 19:40, Markus Teich wrote:
> I assume this is the same issue for slock. From XGrabKeyboard(3):
> > If the keyboard is actively grabbed by some other client, XGrabKeyboard
> > fails
> > and returns AlreadyGrabbed.
> For screenlockers grabbing the keyboard is a must so no other cl
On 2016-01-11 at 09:21, Markus Teich wrote:
> I was not aware of that issue. The man page of unclutter says for the `-grab`
> option "This often doesn't interoperate too well with some window managers" so
> it might actually be not slocks fault. Since this does not seem to be a
> critical
> issue,
Hello
I've noticed that slock won't lock the screen if unclutter grabbed to mouse
pointer. To be precise, the screen blacks for a short moment, and then returns
to the desktop without password verification.
This happens when
$ unclutter -grab
was called more than 5 seconds before, or immediatel
