On Sun, Sep 27, 2015 at 04:37:10PM +0200, Mattias Andrée wrote:
On Sun, 27 Sep 2015 16:30:47 +0200
Markus Teich wrote:
Mattias Andrée wrote:
> Nick wrote:
> > Wouldn't it make sense to add this functionality
> > directly to slock?
>
> Yes it would. Of course, it needs to be optional.
>
> My
Actually, I don't use slock, or any screen
locker, so I don't have a patch.
On Sun, 27 Sep 2015 16:54:47 +0200
Markus Teich wrote:
> Mattias Andrée wrote:
> > The timer support should not be added. However,
> > temporary removal of the terminate-option is important
> > and should be added. But
Mattias Andrée wrote:
> The timer support should not be added. However, temporary removal of the
> terminate-option is important and should be added. But it should be added as a
> wrapper script, so that everyone who uses slock does not need to write their
> own wrapper.
Heyho Mattias,
that would
On Sun, 27 Sep 2015 16:30:47 +0200
Markus Teich wrote:
> Mattias Andrée wrote:
> > Nick wrote:
> > > Wouldn't it make sense to add this functionality
> > > directly to slock?
> >
> > Yes it would. Of course, it needs to be optional.
> >
> > My university have a rule that you may not lock the
>
Mattias Andrée wrote:
> Nick wrote:
> > Wouldn't it make sense to add this functionality directly to slock?
>
> Yes it would. Of course, it needs to be optional.
>
> My university have a rule that you may not lock the computer for more than 10
> minutes, thus it is required that students can pre
On Sun, 27 Sep 2015 15:05:29 +0100
Nick wrote:
> Quoth Mattias Andrée:
> > You could write a wrapper that use setxkbmap
> > to remove the terminate-option, and restore
> > it when slock exits.
>
> Wouldn't it make sense to add this functionality directly
> to slock?
>
Yes it would. Of course,
Quoth Mattias Andrée:
> You could write a wrapper that use setxkbmap
> to remove the terminate-option, and restore
> it when slock exits.
Wouldn't it make sense to add this functionality directly to slock?
On Sun, Sep 27, 2015 at 03:49:17PM +0200, Mattias Andrée wrote:
You could write a wrapper that use setxkbmap
to remove the terminate-option, and restore
it when slock exits.
Thanks.
--
_
< Do what you like, like what you do. >
--
You could write a wrapper that use setxkbmap
to remove the terminate-option, and restore
it when slock exits.
On Sun, 27 Sep 2015 21:42:11 +0800
Pickfire wrote:
> On Sun, Sep 27, 2015 at 02:15:02PM +0200, 7heo wrote:
> >Put
> >
> >if ! pgrep xinit >/dev/null; then
> > start-stop-daemon -S -b s
On Sun, Sep 27, 2015 at 02:15:02PM +0200, 7heo wrote:
Put
if ! pgrep xinit >/dev/null; then
start-stop-daemon -S -b startx
clear
exit
fi
At the end if your ~/.${SHELL}rc file.
What do you mean by that? I mean to disable Xorg Termination when using
`slock`.
--
_
Put
if ! pgrep xinit >/dev/null; then
start-stop-daemon -S -b startx
clear
exit
fi
At the end if your ~/.${SHELL}rc file.
On Sun, Sep 27, 2015 at 06:50:17PM +0800, Pickfire wrote:
> Hi, I set the xorg termination with `localectl`. When using `slock`, I
> press Ctrl+Alt+Backspace and it works, the Xorg is killed and go back to
> the shell. What should I do to prevent that or is there a patch for it?
>
Assuming you st
Hi, I set the xorg termination with `localectl`. When using `slock`, I
press Ctrl+Alt+Backspace and it works, the Xorg is killed and go back to
the shell. What should I do to prevent that or is there a patch for it?
--
_
< Do what you like, like what you do. >
13 matches
Mail list logo
