Here's what I have in my config. I have tried both with and without
shell=True, but it does not seem to want to write the output of xdotool to
whatever window I have highlighted. Any ideas?
Key(["control", "shift"], "j", lazy.spawn("xdotool key 4")),
Thanks!
Alex
On Friday, April 12, 2024 at 1:52:25 PM UTC-5 Tycho Andersen wrote:
> On Fri, Apr 12, 2024 at 10:05:59AM -0500, Alex Becker wrote:
> > Tycho
> >
> > Thanks for the KeyChords idea, I'll have to check that out. Having a
> > separate keyboard "mode" for numpad and whatever other macros I can
> scheme
> > up could have a lot of benefit
> >
> > I think my main issue was with the xdotool component. The command works
> as
> > intended when I run it from a standalone terminal, but for whatever
> reason
> > it doesn't type the input on my screen when I map it out in Qtile.
> Without
> > knowing how exactly everything is set up, I'm guessing the output of the
> > xdotool command is going to some internal shell/process rather than my
> > session. Just a guess
>
> It should go to the screen that is currently highlighted. xdotool
> doesn't print anything to its stdout/err by default, so it mostly
> doesn't matter where that goes (qtile hooks stdout/err to /dev/null
> anyway when it spawns things).
>
> 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 qtile-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/qtile-dev/f3ebf842-4be1-4126-9d85-391d7c6210ben%40googlegroups.com.
