Windows version

[jean-santos]

Experiment disabling tui+termion and using fzf as atuin's frontend.

It seems that the basic functionalities are ok!
I've added a powershell script to remap Ctrl+R and Enter so we can log the commands

The requirements are:

• Having fzf installed
• Specify the path inside the powershell script provided
• Put the powershell script on $profile path (On my PC was ~\Documents\WindowsPowerShell)

Todo:

• Save env variables like RUST_LOG and FZF_DEFAULT_COMMAND on the powershell script to restore then afterwards
• Generate the powershell script via atuin cli
• Write the proper instructions on README.md

This is all I can think of right now

[jean-santos]

By the way, the most relevant match for fzf is different from what (as you can see on the image below, where the query is ls)
atuin search --cmd-only QUERY
outputs now and that will be fixed when #630 is done!

[arcuru]

Just to add a link here because this mentions Windows, switching the backend from termion to crossterm, #331, is how atuin would fully support Windows.

[ellie]

Hey! Thanks for doing the work here, but I don't think we can support windows in any official capacity.

Atm neither @conradludgate nor myself have regular access to a windows box, so releases would not be tested for windows

Given how we can only just support bash (and omg, it has a lot of problems), I don't want to add windows to that list too

I'd be happy to have a build that "might work" for windows, but I wouldn't want to claim that we support it in any way