Wox VS PowerShell

RunFlow is a cross-platform productivity tool which can launch apps and search files and more, that similar to Wox and PowerToys on Windows, and also similar like Alfred and Raycast on macOS. But we have differences with these tools, and we have our own unique new features. Right now, at the below, we will introduce you what features of RunFlow have been implemented in more details. It's an amazing journey, let's start.

I find Wox (which also uses Everything) a really great quick launcher, it saves a lot of time.

https://github.com/Wox-launcher/Wox

Maybe it's Wox (https://github.com/Wox-launcher/Wox) which is no longer maintained. Out of all these Spotlight alternatives, I think Fluent search is the best https://github.com/adirh3/Fluent-Search

Wox

I shared the exact same sentiment when I transitioned to Windows after a long period of only using macOS. I eventually began building a launcher myself using C# and over time it has become my daily driver. Feel free to check it out at https://github.com/dkgv/pinpoint, PRs welcome :-)

A few other nice candidates I found include:

- Keypirinha: https://keypirinha.com/

- Wox: https://github.com/Wox-launcher/Wox

- ueli: https://github.com/oliverschwendener/ueli

Other options that are open source are wox, cerebro and flow launcher

Have a look at PowerToys Run - based on Wox, open-source, and officially MS-backed.

For anyone in need of a functional search in windows: I recommend Wox, it uses the everyhig searoh engine and it works flawlessly

Personally I avoid the start menu or anything related to Windows indexing. What I use is everything and wox.

I'll take this moment to point out that the PowerShell feels like a modern shell and is open source https://github.com/PowerShell/PowerShell (MIT license). If you want something more modern give it a try. Native support for JSON and XML and parallel streams.

That said, I'm glad to see another major release of Fish because it's for having option that we get evolution.

Download: https://github.com/PowerShell/PowerShell/releases/download/v7.4.5/PowerShell-7.4.5-win-x64.msi

PowerShell is so alien to an experienced bash/zsh/etc. user that it's an entirely different language not any kind of drop-in replacement. Its designers also refuse to add simple things to make the switch any easier (e.g. https://github.com/PowerShell/PowerShell/issues/3316).

Not necessarily:

1. UNIX-compatibility aliases like "ls -> Get-ChildItem" and "cat -> Get-Content" are not defined in PowerShell on Linux or macOS. For a complete list of these, see the PowerShell source code[1] (look for "#if !UNIX").

2. A number of aliases from PowerShell ≤ 5.1 were removed in PowerShell Core (≥ 6.0), including the particularly annoying "curl -> Invoke-WebRequest" (conflicts with curl.exe) and "sc -> Set-Content" (conflicts with sc.exe).

[1] https://github.com/PowerShell/PowerShell/blob/8ea1598964590b...

and do a no-install copy-paste deployment of powershell 7 and modules. (I'm not saying you should do this instead of using Lua, just that you can).

[1] https://github.com/PowerShell/PowerShell/releases

msiexec.exe /package https://github.com/PowerShell/PowerShell/releases/download/v7.2.6/PowerShell-7.2.6-win-x64.msi /quiet ADD_EXPLORER_CONTEXT_MENU_OPENPOWERSHELL=1 ADD_FILE_CONTEXT_MENU_RUNPOWERSHELL=1 ENABLE_PSREMOTING=1 REGISTER_MANIFEST=1 USE_MU=1 ENABLE_MU=1 ADD_PATH=1

This smells like when PowerShell aliased curl and wget to a completely different command, with incompatible arguments.

https://github.com/PowerShell/PowerShell/pull/1901