cw does not work in integrated vscode terminal #19
-
Checks
Expected behaviourcw is working in vscode integrated terminal Actual behaviourdoesn't work. (It does work in another terminal - Iterm2)
Steps to reproduceNo response EnvironmentCODEWHISPERER-details:
- 0.12.0
hardware-info:
- model:
- model-id:
- chip-id: Apple M3 Pro
- cores: 11
- mem: 18.00 GB
os-info:
- macOS 14.1.0 (23B2073)
environment:
- shell: /bin/zsh
- terminal: vscode
- cwd: /Users/ronenkonfortes/work/rewire
- exe-path: /Users/ronenkonfortes/.local/bin/cw
- install-method: brew
- env-vars:
- CW_SET_PARENT_CHECK: 1
- __CFBundleIdentifier: com.microsoft.VSCode
- CW_TERM: 0.12.0
- PATH: /Users/ronenkonfortes/work/google-cloud-sdk/bin:/Users/ronenkonfortes/.nvm/versions/node/v16.20.2/bin:/opt/homebrew/Cellar/pyenv-virtualenv/1.2.1/shims:/Users/ronenkonfortes/.pyenv/shims:/Users/ronenkonfortes/.pyenv/bin:/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/ronenkonfortes/work/google-cloud-sdk/bin:/Users/ronenkonfortes/.nvm/versions/node/v16.20.2/bin:/opt/homebrew/Cellar/pyenv-virtualenv/1.2.1/shims:/Users/ronenkonfortes/.pyenv/bin:/opt/homebrew/bin:/opt/homebrew/sbin:/Users/ronenkonfortes/.local/bin
- TERM: xterm-256color
- CWTERM_SESSION_ID: 5052ff9786374d14a551cfc179d5af1a
- SHELL: /bin/zsh
- CW_SET_PARENT: 5052ff9786374d14a551cfc179d5af1a
- ZDOTDIR: /Users/ronenkonfortes
|
Beta Was this translation helpful? Give feedback.
Answered by
konfortes
Nov 28, 2023
Replies: 2 comments 1 reply
-
Try the following:
Let me know how this goes |
Beta Was this translation helpful? Give feedback.
1 reply
-
I found out that my cw vscode integration was toggled off. Turning it on + vscode restart + cw restart did the trick for me |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
grant0417
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I found out that my cw vscode integration was toggled off. Turning it on + vscode restart + cw restart did the trick for me