On Wed, Jan 27, 2016 at 11:31:04PM +0100, FRIGN wrote:
> On Thu, 28 Jan 2016 11:26:48 +1300
> David Phillips wrote:
>
> Hey David,
>
> > You have reminded me, however, that one regret I have since implementing
> > this behaviour is that pressing a modifier key (especially the shift key)
> > will
On Thu, 28 Jan 2016 11:26:48 +1300
David Phillips wrote:
Hey David,
> You have reminded me, however, that one regret I have since implementing
> this behaviour is that pressing a modifier key (especially the shift key)
> will turn the screen red, since a keypress has occurred and the password
>
On Wed, Jan 27, 2016 at 05:16:55PM +0100, FRIGN wrote:
> On Wed, 27 Jan 2016 13:58:56 -0200
> Brad Luther wrote:
>
> Hey Brad,
>
> > I think I found a bug on slock.
>
> No this is not a bug.
>
> > If you're typing your password and gets a char wrong, you go and
> > delete the char, then contin
Brad Luther wrote:
> But if the behavior for Markus is different, then his slock is bugged :)
Heyho Brad,
nope, I just have the failonclear set to false in config.h. Then the empty input
state only turns red after a failed attempt. Otherwise it always is red except
right after starting slock. And
On Wed, 27 Jan 2016 19:28:37 -0200
Brad Luther wrote:
Hey Brad,
> So the screen:
> --- turns blue when any key is pressed
> --- turns red when a failed password is entered OR an entire buffer is deleted
> Following this logic, then it really isn't a bug.
you can describe it like this: The scree
But if the behavior for Markus is different, then his slock is bugged :)
I am on git HEAD, yes.
Try updating and see if that fixes it.
Thanks.
On Wed, Jan 27, 2016 at 7:28 PM, Brad Luther wrote:
> So the screen:
> --- turns blue when any key is pressed
> --- turns red when a failed password is e
So the screen:
--- turns blue when any key is pressed
--- turns red when a failed password is entered OR an entire buffer is deleted
Following this logic, then it really isn't a bug.
Thanks.
On Wed, Jan 27, 2016 at 2:16 PM, FRIGN wrote:
> On Wed, 27 Jan 2016 13:58:56 -0200
> Brad Luther wrote
On Wed, 27 Jan 2016 13:58:56 -0200
Brad Luther wrote:
Hey Brad,
> I think I found a bug on slock.
No this is not a bug.
> If you're typing your password and gets a char wrong, you go and
> delete the char, then continue to type the pass and 'enter' to unlock
> the screen. All good, screen is b
Brad Luther wrote:
> If you're typing your password and gets a char wrong, you go and delete the
> char, then continue to type the pass and 'enter' to unlock the screen. All
> good, screen is blue all the time. Unless... you get the first char wrong. If
> you mistype the first char of your passwor
Hello.
I think I found a bug on slock.
If you're typing your password and gets a char wrong, you go and
delete the char, then continue to type the pass and 'enter' to unlock
the screen. All good, screen is blue all the time.
Unless... you get the first char wrong. If you mistype the first char
of
10 matches
Mail list logo
