Re: [9front] rio-dependence of screenlock

[ori@eigenstate.org]

Quoth Stuart Morrow <morrow.stuart@gmail.com>:
> How screenlock works:
> 
> 1. Get screen size
> 2. Create new Rio window with that size, ignore return value
> 3. for(;;) warp mouse to centre.
> 
> There are two ways to do 1.  From the shell, they are:
> 
> A%  file /dev/screen
> B%  awk '{print $7"x"$8}' /dev/draw/new
> 
> Screenlock uses A. On the system console, you can in fact run
> screenlock by binding any static image over stub(4)'s /dev/screen.
> Recall that we don't check if we *actually got* a Rio window.
> 
> My patch uses B.  Runs on the system console just fine. In a nested
> Rio, no different from current.  It also tops itself so that a popup's
> right-click menu can't be used to delete it.  Popups aren't really the
> style on Plan 9, but one can easily imagine a script that catches
> kprints and tops a normally-hidden window.
> 
> I'll throw you a quid, whoever writes that.  I'd like to test that I know
> how to use Bitcoin, which seems the best way to do bounties (everyone
> can verify in blockchain.info, or in a local copy of the blockchain, that
> the payment was made and received).  Or Bitcoin Cash if you insist on
> something you can actually run on Plan 9.
>

The patch seems reasonable to me.