On Wed, Dec 17, 2014 at 03:36:52PM +0100, Fabien Meghazi wrote:
> On Fri, Dec 12, 2014 at 2:55 PM, Tycho Andersen <[email protected]> wrote:
> > I'm not sure you can alias keys right now, although it shouldn't be
> > too hard to add (untested):
> >
> > commit a863863ca841463abcbcf871fc52b20e6e11e05f
> > Author: Tycho Andersen <[email protected]>
> > Date:   Fri Dec 12 07:53:37 2014 -0600
> >
> >     add lazy.fake_keypress('r')
> 
> Thanks for your commit, this works with normal keys,
> unfortunately the XF86Copy, XF86Paste, ... etc seems to be ignored by
> everyone and thus has no effect.

Sorry, it looks like there was a typo in my message below...

> > ..and then do something like:
> >
> > Key([mod], "c", lazy.fake_keypress("X86Copy")),
> > Key([mod], "v", lazy.fake_keypress("X86Paste")),

These should be XF86Copy, instead of X86Copy; did you copy and paste
my error perhaps?

> So I wonder if it's possible to make this fake_keypress() function to
> actually simulate multiple keystrokes like Ctrl+C, Ctrl+P

I think so, you'll just have to set the right state bits in the event
you send to qtile. I can post a patch for that if you want.

> I know that other tools such as xbindkeys would be more appropriate
> but as I want to put some logic behind (eg: on Win+C keystroke, send
> Ctrl+C instead except if current focuses application is a terminal) I
> find it appropriate in my use case to put it in my qtile config.

No problem, it seems like a reasonable thing to want to do, so I don't
have any issue with building better support for it.

Tycho

> -- 
> You received this message because you are subscribed to the Google Groups 
> "qtile-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
You received this message because you are subscribed to the Google Groups 
"qtile-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to