Version: 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T13:20:50.359Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-47-generic
- Local OS Version: Ubuntu 20.04 LTS 5.4.0-47-generic (update to the latest)
- Remote OS Version: CentOS 7 3.10.0-1127.19.1.el7.x86_64 (update to the latest) on VMWare
- Remote Extension/Connection Type: SSH
Steps to Reproduce:
1.ssh to the guest machine;
2. using git rebase branch and try to resolve conflicts in vscode, and when committing the changes, a window prompts and says "Terminal is dumb, but EDITOR unset", stackoverflow says this happens when you editing conflicts using editors other than vim but the env EDITOR is unset.
Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No
Version: 1.49.0
Commit: e790b931385d72cf5669fcefc51cdf65990efa5d
Date: 2020-09-10T13:20:50.359Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-47-generic
Steps to Reproduce:
1.ssh to the guest machine;
2. using
git rebase branchand try to resolve conflicts in vscode, and when committing the changes, a window prompts and says "Terminal is dumb, but EDITOR unset", stackoverflow says this happens when you editing conflicts using editors other than vim but the env EDITOR is unset.Does this issue occur when you try this locally?: No
Does this issue occur when you try this locally and all extensions are disabled?: No