Hey,
Wouldn't follwing patch solve your problem?:
https://tools.suckless.org/slock/patches/control-clear
Regards,
Michael
Am Mo., 27. Aug. 2018 um 20:18 Uhr schrieb Michael Spradling
<m...@mspradling.com>:
>
> Currently if the first character pressed is the shift key, slock moves
> to the failed state. The failed state can modify the display and
> provide incorrect feedback to the user and also gives away that your
> first character required the shift key.
> ---
> slock.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/slock.c b/slock.c
> index 5ae738c..e9dd1ad 100644
> --- a/slock.c
> +++ b/slock.c
> @@ -154,7 +154,9 @@ readpw(Display *dpy, struct xrandr *rr, struct lock
> **locks, int nscreens,
> IsKeypadKey(ksym) ||
> IsMiscFunctionKey(ksym) ||
> IsPFKey(ksym) ||
> - IsPrivateKeypadKey(ksym))
> + IsPrivateKeypadKey(ksym) ||
> + ksym == XK_Shift_L ||
> + ksym == XK_Shift_R)
> continue;
> switch (ksym) {
> case XK_Return:
> --
> 2.18.0
>
>
