Wrong autocomplete position #47
-
Checks
Expected behaviourThe suggestion popup is positioned right below the cursor. Actual behaviourThe suggestion popup is positioned in the center of the screen. Steps to reproduceJust open any kind of terminal. EnvironmentCODEWHISPERER-details:
- 0.13.0
hardware-info:
- model:
- model-id:
- chip-id: Intel(R) Core(TM) i7-7820HQ CPU @ 2.90GHz
- cores: 4
- mem: 16.00 GB
os-info:
- macOS 13.3.1 (22E772610a)
environment:
- shell: /bin/zsh
- terminal: intellij-webstorm
- cwd: /Users/username/WebstormProjects/projectname/ionic
- exe-path: /Users/username/.local/bin/cw
- install-method: unknown
- env-vars:
- CWTERM_SESSION_ID: c9050994084a49b280d0a77e0db3bd8c
- CW_SET_PARENT_CHECK: 1
- CW_TERM: 0.13.0
- PATH: /Users/username/.pyenv/shims:/opt/local/bin:/opt/local/sbin:/Library/Frameworks/Python.framework/Versions/3.10/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/apache-maven-3.8.6/bin:/Library/Apple/usr/bin:/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/username/WebstormProjects/projectname/ionic/node_modules/.bin:/Users/username/.local/bin
- SHELL: /bin/zsh
- TERM: xterm-256color
- __CFBundleIdentifier: com.jetbrains.WebStorm
- CW_SET_PARENT: c9050994084a49b280d0a77e0db3bd8c |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Beta Was this translation helpful? Give feedback.
-
fwiw, I was seeing this behavior also (I'm not op). I am running multiple monitors on macOS 14.2.1 and Alacrity + tmux. Checkmarks & cw doctor all green It eventually went away after a reboot. Unclear what triggers it. |
Beta Was this translation helpful? Give feedback.
-
Seems like this issue was resolved by OP. Sometimes this happens. It means we are struggling to identify where your typing cursor is. Best fix: run |
Beta Was this translation helpful? Give feedback.
I also haven't noticed this buggy behaviour in a while now. It might have been fixed already.