PSFzf VS Windows Terminal

Sets up PSFzf: PowerShell wrapper for fzf, for fuzzy finding files and directories

# To make ZLocation module work in every PowerShell instance. Import-Module ZLocation # PSFzf has undocumented option to use fd executable for # file and directory searching. This enables that option. Set-PsFzfOption -EnableFd:$true # Custom function to SetLocation, because PSFzf uses # Get-ChildItem which doesn't use fd and doesn't use # ignore files. Invoke-FuzzySetLocation is defined here # https://github.com/kelleyma49/PSFzf/blob/b97263a30addd9a2c84a8603382c92e4e6de0eeb/PSFzf.Functions.ps1#L142 # # This implementation is for setting FileSystem location # and implementation uses parts of # https://github.com/kelleyma49/PSFzf/blob/b97263a30addd9a2c84a8603382c92e4e6de0eeb/PSFzf.Base.ps1#L20 # https://github.com/kelleyma49/PSFzf/blob/b97263a30addd9a2c84a8603382c92e4e6de0eeb/PSFzf.Base.ps1#L35 function Invoke-FuzzySetLocation2() { param($Directory = $null) if ($null -eq $Directory) { $Directory = $PWD.Path } $result = $null try { # Color output from fd to fzf if running in Windows Terminal $script:RunningInWindowsTerminal = [bool]($env:WT_Session) if ($script:RunningInWindowsTerminal) { $script:DefaultFileSystemFdCmd = "fd.exe --color always . {0}" } else { $script:DefaultFileSystemFdCmd = "fd.exe . {0}" } # Wrap $Directory in quotes if there is space (to be passed in fd) if ($Directory.Contains(' ')) { $strDir = """$Directory""" } else { $strDir = $Directory } # Call fd to get directory list and pass to fzf Invoke-Expression (($script:DefaultFileSystemFdCmd -f '--type directory {0} --max-depth 1') -f $strDir) | Invoke-Fzf | ForEach-Object { $result = $_ } } catch { } if ($null -ne $result) { Set-Location $result } } # Show tips about newly added commands function Get-Tips { $tips = @( [pscustomobject]@{ Command = 'fcd' Description = 'navigate to subdirectory' }, [pscustomobject]@{ Command = 'ALT+C' Description = 'navigate to deep subdirectory' }, [pscustomobject]@{ Command = 'z' Description = 'ZLocation' }, [pscustomobject]@{ Command = 'fz' Description = 'ZLocation through fzf' }, [pscustomobject]@{ Command = 'fe' Description = 'fuzzy edit file' }, [pscustomobject]@{ Command = 'fh' Description = 'fuzzy invoke command from history' }, [pscustomobject]@{ Command = 'fkill' Description = 'fuzzy stop process' }, [pscustomobject]@{ Command = 'fd' Description = 'find https://github.com/sharkdp/fd#how-to-use' }, [pscustomobject]@{ Command = 'rg' Description = 'find in files https://github.com/BurntSushi/ripgrep/blob/master/GUIDE.md' } ) Write-Output $tips | Format-Table } # Define aliases to call fuzzy methods from PSFzf New-Alias -Scope Global -Name fcd -Value Invoke-FuzzySetLocation2 -ErrorAction Ignore New-Alias -Scope Global -Name fe -Value Invoke-FuzzyEdit -ErrorAction Ignore New-Alias -Scope Global -Name fh -Value Invoke-FuzzyHistory -ErrorAction Ignore New-Alias -Scope Global -Name fkill -Value Invoke-FuzzyKillProcess -ErrorAction Ignore New-Alias -Scope Global -Name fz -Value Invoke-FuzzyZLocation -ErrorAction Ignore

Are you using PSFzf or something else? https://github.com/kelleyma49/PSFzf

kelleyma49/PSFzf: A PowerShell wrapper around the fuzzy finder fzf — https://github.com/kelleyma49/PSFzf

> convince management of the value

This presupposes that such convincing is even possible. Many, many companies have leadership that are simply terrible at identifying value. If you've never been part of a majority of developers advocating for, if not outright begging for, some huge ROI initiative to get the green light, you are very fortunate.

There are great counterexamples, like Valve, which is known for giving developers an extreme degree of autonomy, and they benefit greatly from that approach. For each Valve, though, there are dozens of companies that manage to succeed despite themselves.

Take Microsoft, for example. One tiny, yet representative, example: the way the Windows Terminal team handled a suggestion from Casey Muratori to take their software from abysmally slow to lightning fast:

https://github.com/microsoft/terminal/issues/10362

A quote from one of the Terminal developers, dismissing the suggestion:

> I believe what you’re doing is describing something that might be considered an entire doctoral research project in performant terminal emulation as “extremely simple” somewhat combatively…

Just how difficult was such an endeavor in actuality? Well, given that Casey implemented his own terminal emulator from scratch and incorporated the functionality he was proposing in a mere weekend... not a whole lot. Relatively minor effort for a huge return on investment. It took Casey explaining the concepts, then providing a working proof of concept, and finally a bunch of backlash online towards the Terminal team to get them to do the right thing for themselves and their users.

At this point ConHost.exe is open source [0] so it is maybe not a stretch to expect Microsoft to open source CMD.EXE at some point.

Though with PowerShell being cross-platform and already open source, I personally don't think there's enough to gain in some sort of better open source CMD.EXE fork. I'd be interested in being proved wrong on that, but I'm also happy enough with PowerShell these days I'm not in a hurry to return to CMD.EXE.

[0] https://github.com/microsoft/terminal/tree/main/src/host

"Users of Linux and macOS may well be familiar with the sudo command, used regularly in the terminal, and it looks like Windows may finally be getting its own version."

More Linux tools are coming to Windows, especially Windows Server because the tools are good and they make it easier to administer a Windows Server.

They are looking at adding a default TUI text editor (https://github.com/microsoft/terminal/discussions/16440) and now they are adding sudo.

I would not be surprised if systemd or something like it gets ported or reinvented for Windows simply because it makes managing services so nice.

GitHub

>We are allowed to view and consume it, to be influenced by it, and under many circumstances even outright copy it.

People keep saying this but it's actually much more complicated, and in many cases you can't view copyrighted content.

An example, MicroSoft employees are not permitted to view or learn from an open source (GPL-2) terminal emulator:

https://github.com/microsoft/terminal/issues/10462#issuecomm...

Another example is proprietary software that may have it's source available, either intentionally or not. If you view this and then work on something related to it, like WINE for example, you are definitely at risk of being successfully sued.

If you worked at MicroSoft and worked on Windows, you would not be able to participate in WINE development at all without violating copyright.

If you viewed leaked Windows source code you also would not be able to participate in WINE development.

An interesting question that I have, is whether training on proprietary, non-trade-secret sources would be allowed. Something like unreal engine, where you can view the source but it's still proprietary.

Windows Terminal is pretty good and a new terminal emulator written in the last few years. No smooth scrolling, here's the GitHub issue requesting it: https://github.com/microsoft/terminal/issues/1400

Assume its related to this:

https://github.com/microsoft/terminal/issues/10362

It's nothing serious just microsoft engineers writing slow as shit code and reacting poorly to someone trying to help.

"There are plenty of offline scenarios where this would be incredibly useful. For disconnected environments, etc. There are some environments that will never connect to winget."

Source: https://github.com/microsoft/terminal/discussions/16440#disc...