4 ms·
I noticed that you're using macOS's Accessibility API to provide your autocompletions. That's a clever use, and it sidesteps a huge source of pain when trying t
by woodruffw 5y ago
I noticed that you're using macOS's Accessibility API to provide your autocompletions. That's a clever use, and it sidesteps a huge source of pain when trying to make terminals smarter (i.e., dealing with the TTY/PTY layers, terminal capabilities, &c).
My question, since you mentioned that Linux support is "not an afterthought": how do you intend to support Linux? Your architecture on macOS is essentially a (benign) keylogger that I'm liable to trust because of Apple's strong isolation of concerns/entitlements; no such isolation is (consistently) available across Linux distributions. I suspect that most developers on Linux won't want your proprietary client running as a logger over X11 or Wayland.
- brendanfalk 5y agoEarly versions of Fig essentially used a keylogger to predict what you had typed in the terminal. This is not optimal from a security or product standpoint. We have since integrated with the shells themselves (e.g. with zsh's line editor, ZLE for zsh). This allows us to get what you've typed more accurately and for your shell only. We are also working on new integration done exclusively through pseudoterminals. Both of the cases above mean our Linux integration will simply be for window management! You can see how all of our integrations with bash, zsh, fish, SSH, Docker etc work here: https://github.com/withfig/config https://github.com/withfig/config
- woodruffw 5y agoThanks for the response! It's good to know you've moved away from that approach. I'm probably not one of your end users (I'd prefer an open-source or source-available client), but I look forward to seeing the progress you make on this.