Open qubist opened 2 years ago
Hey @qubist! Thanks for letting us know. My suggestion is to use enter or tab to select suggestions. Using a keyboard to insert suggestions prevents focus from switching between the terminal and Fig.
Thanks @mschrage, that's what I normally do. Ideally, though, the described behavior would not happen.
Description:
Clicking on an option in the Fig autocomplete menu removes focus from iTerm, requiring me to click on the window in order to type again. Breaks flow :(
Here's a video: Note when my cursor changes from solid to outlined. While it is outlined (window unfocused) I try in vain to continue typing. Only after clicking can I type again.
https://user-images.githubusercontent.com/3607279/157787464-737ed48a-3237-45d3-98ac-e60851a6ac9e.mov
Details:
fig diagnostic
# Fig Diagnostics ## Fig details: - Fig version: Version 1.0.56 (B402) [Beta] - Bundle path: /Applications/Fig.app - Autocomplete: true - Settings.json: true - Accessibility: true - Number of specs: 0 - Symlinked dotfiles: false - Only insert on tab: false - Keybindings path: - Installation Script: true - PseudoTerminal Path:
- SecureKeyboardInput: false
- SecureKeyboardProcess:
## Hardware Info:
- Model Name: MacBook Pro
- Chip: Apple M1
- Cores: 8 (4 performance and 4 efficiency)
## OS Info:
- macOS 12.1.0
## Environment:
- User Shell: /bin/zsh
- CLI Installed: true
- Executable Location: /usr/local/bin/fig
- Current Window ID: XXX (com.googlecode.iterm2)
- Environment Variables:
- TERM=xterm-256color
- FIG_INTEGRATION_VERSION=8
- FIG_TERM=1
- FIG_TERM_VERSION=4.1.3
- FIG_CHECKED_PROMPTS=1
## Integrations:
- SSH: false
- TMUX: false
- iTerm: installed!
- Hyper: application is not present.
- Visual Studio Code: installed!
- Docker: false
Edited some of this for privacy. If needed I can provide. I think you should probably warn before publicly posting people's PATHs and stuff.