Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fig suggestion screen jumps to other screen when having multiple screens on MacOS #57

Closed
Fabio-GC opened this issue Apr 22, 2021 · 2 comments
Labels
type:bug Something isn't working

Comments

@Fabio-GC
Copy link

Fabio-GC commented Apr 22, 2021

Description:

When having two screens ( one over the other ) and we open VS on the screen that is on the top, being the terminal in the bottom part of the screen, when typing something on the terminal, the fig recommendations pop-up will appear in the bottom screen instead of the top screen, where the terminal is.

This is happening in a MacBook Pro.

Screenshot 2021-04-22 at 14 17 21

Details:

macOS Fig Shell
10.16.0 Version 1.0.40 (B188) /bin/zsh
fig diagnostic

Version 1.0.40 (B188)
UserShell: /bin/zsh
Bundle path: /Volumes/fig/Fig.app
Autocomplete: true
Settings.json: true
CLI installed: true
CLI tool path: /Users/fabiocalandruccioespino/.fig/bin/fig
Accessibility: true
Number of specs: 77
SSH Integration: true
Tmux Integration: true
Keybindings path: /Users/fabiocalandruccioespino/.fig/user/keybindings
iTerm Integration: false
Hyper Integration: false
VSCode Integration: true
Docker Integration: true
Symlinked dotfiles: false
Only insert on tab: false
Installation Script: true
PseudoTerminal Path: 
SecureKeyboardInput: false
SecureKeyboardProcess: 
Current active process: /bin/zsh (62931) - ttys002
Current working directory: /Users/fabiocalandruccioespino/Documents/crewapp
Current window identifier: 28883/code:62931% (com.microsoft.VSCode)

@mschrage
Copy link
Member

Thanks so much for reporting this. I'll investigate what's going on here.

@mschrage mschrage added the type:bug Something isn't working label Apr 23, 2021
@mschrage
Copy link
Member

This will be fixed in the next release (v1.0.41). Thanks again for creating the issue - wouldn't have caught this otherwise.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants