question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Windows + R bringing up Flow Launcher even when not set as the hotkey

See original GitHub issue

Describe the bug/issue A clear and concise description of what the bug is.

I’ve got my trigger hotkey set to ctrl + space … when I press Winkey + r the FL search bar pops up. This prevents me from using the standard Windows Run hotkey.

To Reproduce Steps to reproduce the behavior: Press Winkey + R …

Screenshots If applicable, add screenshots to help explain your problem.

image

Your System

Windows build number: (run "ver" at a command prompt)
Microsoft Windows [Version 10.0.19043.1415]

Flow Launcher version: (Settings => About) 
1.9.1

Flow Launcher Error Log

2022-01-03.txt

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
STaRDoGGcommented, Jan 3, 2022

@onesounds Maybe FL can detect if the Shell plugin is enabled/installed/Replace Win + R is enabled, and if so, add a text link under the normal hotkey mentioning it, and clicking the link navigates to that plugin’s setting. That would make it more intuitive for people like me, lol.

Another think I just noticed that I’m not sure is intended or not; the > was automatically being added to the search bar when the bar was opened, and selected (highlighted), with nothing after it, presumably to make it a bit easier to run commands. But in order to run a command you’d have to first unhighlight it either manually with a mouse click, or a right arrow, and then start typing. And if you hit the delete/backspace while the > is selected when the bar comes up, it gets deleted, and doesn’t get auto-added the next time the bar comes up. Sort of inconsistent behavior imho.

1reaction
onesoundscommented, Jan 3, 2022

I’ve experienced the same confusion as you at first. First of all, I don’t think it’s a big problem because it indicates that the “>” mark is intended to appear. I’ll think about how to add a simple guide.

And that plug-in is a plug-in that allows you to use shell commands. Try to get used to it.

  • Turn On " Do not close command prompt after command excution"
  • and try this. “> start shell:RecycleBinFolder” or “> ipconfig”
Read more comments on GitHub >

github_iconTop Results From Across the Web

windows key to open Flow with autohotkey script
After Launching the script you need to go into Flow Launcher Settings and set the shortcut by pressing the Windows Key. If its...
Read more >
Increase Your Productivity in Windows With Flow Launcher
Open the Flow Launcher window by pressing the hotkey you chose during setup. · Begin typing the name of the app. · As...
Read more >
Search for files, folders, run programs, commands, web ...
Flow Launcher is an open source tool that can search for files, folders, run programs, commands, web searches from your desktop.
Read more >
Quick Search/Launcher for Windows | Wox, but better - YouTube
It's a completely quick crash course on Flow Launcher. ... Download/ Install Flow Launcher 2:22 - Setting up Flow Launcher 3:20 - Using...
Read more >
Turn off display in Windows on command
On a laptop you can use the keyboard shortcut combination of Fn+F7 (F7 ... This will not turn off you screen but make...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found