GNOME terminal, Terminator, Cmder, Hyper… many shell interfaces and terminal emulators that users swore by. Some offer better functionality, some offer convenience or extended customizability. If you have any insight on how to solve these challenges, please comment below or join our #cross-platform channel on Discord.GNOME terminal, Terminator, Cmder, Hyper… many shell interfaces and terminal emulators that users swore by.

See 'How can I use a bash-like shell on Windows' for more details.

What is the difference between Cygwin, MSYS/MinGW, git bash and WSL? Which should we support? Where are bashrc and bash_profile equivalents located? This entails research & experimentation with how shells work on Windows. We need to install our shell integrations. This is the subsystem that links our TypeScript autocomplete engine with native OS functionality.

We need to port over the Fig.js API to Windows. This can be implemented at the OS level or potentially at the pseudoterminal level. We need intercept certain keystrokes to prevent them from being handled by the shell. We need to be able to position a 'floating' window overlay on top of 3rd party applications. I am not sure about the equivalent on Windows. On macOS (and Linux) we use UNIX domain sockets. We need to do IPC between our CLI tools and our GUI app. We need to do some research to understand how this should work on a non-UNIX system. This means porting our pseudoterminal layer ( figterm) to Window. We need to be able to determine what you've typed in the terminal.This seems possible using Microsoft Active Accessibility APIs. We need to be able to determine the location of the cursor in a 3rd party app.There are at least 7 core functions that need to be built out in order for us to release autocomplete to Windows. We are super excited about bringing Fig to Windows, but there is lots of work to do before this is possible. Hey everyone! Thank you for your patience.

Equivalent hyperterminal windows 10