hiro wrote:
> How does your integrated execution of s2ram change that? Your slock can still
> fail in just the same way.
Heyho hiro,
with the patch first the cover window is created and the keyboard and mouse are
grabbed. I consider this setup. If it fails, slock exits and does *not* execute
On Mon, Jan 18, 2016 at 08:24:14AM +0100, Jan Christoph Ebersbach wrote:
> - I miss that I can't align multiple cursors in insert mode, i.e. to
> align all "=" over multiple lines. The editor kakoune supports this
> nicely
I just implemented basic support for this with Shift-Tab in
On Tue, Feb 09, 2016 at 10:01:30PM +0100, FRIGN wrote:
> On Tue, 09 Feb 2016 21:49:17 +0100
> Christoph Lohmann <2...@r-36.net> wrote:
>
> > Which OS are you using?
> > Which distribution of this OS are you using?
> > Which webkit version are you using?
> > Have you compiled webkit on your own?
>
stdout could print an api secret "[locked]" and the calling script could act
upon that.
slock | {
read
if [[ "$REPLY" = "[locked]" ]]; then
suspend
else
yell at user or power off for added security
fi
}
cheers!
mar77i
Oh god no.
You guys must have some strange use cases.
When I run slock there's no way for me to miss whether it ran or not
(It is pretty visible all over my screen). So I have like 1 second to
notice this before my display shuts off for standby. In the unlikely
event of catastrophic X-Bullshit I
you can already use xssstate to monitor the state of the screen and
the screensaver, why not use that to do both slock, and eventually
sleep?
--Carlos
On Sat, Feb 13, 2016 at 3:57 PM, hiro <23h...@gmail.com> wrote:
> Oh god no.
>
> You guys must have some strange use cases.
>
> When I run slock
On Sat, 13 Feb 2016 21:57:14 +0100
hiro <23h...@gmail.com> wrote:
Hey hiro,
> When I run slock there's no way for me to miss whether it ran or not
> (It is pretty visible all over my screen). So I have like 1 second to
> notice this before my display shuts off for standby. In the unlikely
>
i.e. throw out all this platform dependent bullshit password checking
code and replace it with simple string comparison (string from text
file).
Recently, the question of the correctness of vim's behavior of 2dw on
the first of three lines of one word each came up on the vim mailing
list (it turns out that it's not correct according to POSIX, but is
shared with traditional vi).
At that time, I wasn't able to build vis to see what it
