From: Laurence Perkins <lperkins@openeye.net>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Re: escape from i3lock
Date: Thu, 11 Jul 2019 21:10:54 +0000 [thread overview]
Message-ID: <2e7820e8c6ef5aaa4e0b7852a66b873ad1915452.camel@openeye.net> (raw)
In-Reply-To: <cone.1562878861.552236.2036.1000@epsilon>
[-- Attachment #1: Type: text/plain, Size: 2128 bytes --]
You could also leave DontVTSwitch on all the time and set a keyboard
shortcut to run chvt (man 1 chvt) with appropriate permissions and
parameters instead. Keyboard shortcuts shouldn't get processed if the
screen is locked.
LMP
On Thu, 2019-07-11 at 21:01 +0000, artur.tamm.85@gmail.com wrote:
> I tried to google if it is possible to change xorg serverflags in
> runtime,
> but was unable to find anything. I think that would be a cleaner
> solution
> (changing the DontVTSwitch option before locking and then restoring
> later).
>
> Artur
>
> Ian Zimmerman writes:
>
> > On 2019-07-11 09:57, Ian Zimmerman wrote:
> >
> > > > setxkbmap -option srvrkeys:none
> > > > i3lock -c 003355 -n
> > > > setxkbmap -option ''
> > >
> > > Thanks for the idea! It won't work as is for me because I
> > > already use
> > > some non-default xkb options. But it is closer than anything
> > > that has
> > > come up yet. I'll get there.
> >
> > Okay, I got it to work in a brute force way: I just added another
> > setxkbmap command to set my normal options, the same ones as in my
> > xorg.conf.
> >
> > But something weird happens when I try the fancy way: saving the
> > options
> > with "setxkbmap -print >FILE" and then restoring them with "xkbcomp
> > FILE". It seems that the change I make with "setxkbmap -option
> > FOO" is
> > never reflected in the output of "setxkbmap -print".
> >
> > Looks like another place with multiple "levels" of configuration
> > stepping over each other.
> >
> > --
> > Please don't Cc: me privately on mailing lists and Usenet,
> > if you also post the followup to the list or newsgroup.
> > To reply privately _only_ on Usenet and on broken lists
> > which rewrite From, fetch the TXT record for no-use.mooo.com.
> >
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2019-07-11 21:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 17:03 [gentoo-user] escape from i3lock Ian Zimmerman
2019-07-10 18:44 ` François-Xavier CARTON
2019-07-10 22:48 ` [gentoo-user] " Ian Zimmerman
2019-07-10 23:21 ` artur.tamm.85
2019-07-10 23:46 ` artur.tamm.85
2019-07-11 16:57 ` Ian Zimmerman
2019-07-11 20:47 ` Ian Zimmerman
2019-07-11 21:01 ` artur.tamm.85
2019-07-11 21:10 ` Laurence Perkins [this message]
2019-07-12 0:11 ` David Haller
2019-07-12 1:17 ` Laurence Perkins
2019-07-12 8:48 ` Michele Alzetta
2019-07-11 0:43 ` Adam Carter
2019-07-11 16:49 ` Ian Zimmerman
2019-07-11 20:28 ` Nuno Silva
2019-07-12 16:01 ` Ian Zimmerman
2019-07-12 16:05 ` Michele Alzetta
2019-07-12 16:09 ` Laurence Perkins
2019-07-13 19:11 ` Nuno Silva
2019-07-10 19:23 ` [gentoo-user] " Alec Ten Harmsel
2019-07-10 20:52 ` Neil Bothwick
2019-07-10 21:00 ` Alec Ten Harmsel
2019-07-10 22:45 ` [gentoo-user] " Ian Zimmerman
2019-07-10 21:18 ` [gentoo-user] " Francesco Turco
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2e7820e8c6ef5aaa4e0b7852a66b873ad1915452.camel@openeye.net \
--to=lperkins@openeye.net \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox