Autocompletion window in wrong location for Zed terminal

[brandonweiss]

Checks

• [X] I have searched github.com/withfig/fig/issues and there are no duplicates of my issue
• [X] I have run fig doctor in the affected terminal session
• [X] I have run fig restart and replicated the issue again

Operating system

macOS 13.4.0 (22F66)

Expected behaviour

The autocompletion window should stay near the terminal cursor.

Actual behaviour

The autocompletion window moves to an incorrect position.

Steps to reproduce

I’m not exactly sure how to reproduce it. Sometimes tabbing away and back to the window seems to do it. Sometimes switching tabs, or splitting panes.

Environment

fig-details:
  - 2.16.0
hardware-info:
  - model: 
  - model-id: 
  - chip-id: Apple M2 Pro
  - cores: 12
  - mem: 16.00 GB
os-info:
  - macOS 13.4.0 (22F66)
environment:
  - shell: /bin/zsh
  - terminal: zed
  - cwd: /Users/brandon/Developer/supernormal
  - exe-path: /opt/homebrew/bin/fig
  - install-method: brew
  - env-vars:
    - FIGTERM_SESSION_ID: d734f213-6363-4768-b360-77e7dac3fe01
    - FIG_SET_PARENT_CHECK: 1
    - FIG_TERM: 2.16.0
    - PATH: /Users/brandon/.asdf/shims:/opt/homebrew/opt/asdf/libexec/bin:/Users/brandon/Developer/dotfiles/bin:./bin:./node_modules/.bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/brandon/.rbenv/shims:/opt/homebrew/bin:/opt/homebrew/sbin:/usr/local/bin:/System/Cryptexes/App/usr/bin:/usr/bin:/bin:/usr/sbin:/sbin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/local/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/bin:/var/run/com.apple.security.cryptexd/codex.system/bootstrap/usr/appleinternal/bin:/Users/brandon/.fig/bin:/Users/brandon/.local/bin
    - SHELL: /bin/zsh
    - TERM: xterm-256color
    - __CFBundleIdentifier: dev.zed.Zed
    - FIG_PID: 51756
    - FIG_SET_PARENT: d734f213-6363-4768-b360-77e7dac3fe01

[mschrage]

Looks like Zed may be incorrectly reporting the cursor position to the OS. Can you check if Autocomplete works as expected in Alacritty or Kitty terminal?

[brandonweiss]

Oh, huh. I’ve used Fig with other terminals and it works fine, so it sounds like that might be the issue… do you need me to try it with those two specific terminals for some reason?

[Den4ik]

The same problem with iTerm2. There is no issue with fig 2.15.0