Can't run CommandSet extension
See original GitHub issueThis is split from https://github.com/qtile/qtile/issues/2730
Qtile version: 0.18.2.dev130+g3fe5e0d1
Commit where problem starts: https://github.com/qtile/qtile/commit/4c0988c2e155ff33b0179d22db653454635be814
Xephyr log cannot grab keyboard
Test case
EzKey("M-C-q", lazy.run_extension(extension.CommandSet(
commands={
'a': 'xterm'
},
foreground='#FF0000', selected_background='#FF0000')),
desc='test'),
Issue Analytics
- State:
- Created 2 years ago
- Comments:14 (13 by maintainers)
Top Results From Across the Web
[Fix] Cannot Run Programs Without Typing the Extension ...
If you're unable to launch programs without having to type the extension “.exe” in a Command Prompt window, you need to fix your...
Read more >Build your first ListView Command Set extension
Create an extension project, and then code and debug your extension by using SharePoint Framework (SPFx) Extensions.
Read more >ListView Command Set extension: Error after gulp serve #6402
Repro Steps: SPFx project solution with ListView Command Set extension; Run gulp serve; SharePoint site opened in browser with allow debug ...
Read more >Cannot debug SharePoint Framework command set extension ...
I tried all kinds of debug configurations, but whatever I do the breakpoint in my custom command set extension won't get hit in...
Read more >SPFx List View Command Set Extension - YouTube
SPFx List View Command Set Extension - Adding Command bar buttons & Hiding Details ... The company doesn't want users to bulk edit...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Awesome, I think it should work from X’s point of view, it’s just a matter of us doing it correctly 😃
Thanks for splitting this out. We probably need @m-col to take a look too as the issue arose in that keybinding/swallowing commit.