The current line disappears in terminal with `Ctrl+r` and `Space` when `"terminal.integrated.gpuAcceleration": "off"`
Does this issue occur when all extensions are disabled?: Yes
Version: 1.72.0-insider (Universal) Commit: c4722f1bb292284e0437eb7547808a5788fe6430 Date: 2022-09-02T05:20:22.688Z Electron: 19.0.12 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin arm64 20.6.0 Sandboxed: Yes
The shell is zsh. The settings.json is as follows:
{
"terminal.integrated.gpuAcceleration": "off",
"workbench.colorTheme": "Default Light+",
"window.zoomLevel": 1
}
Steps to Reproduce:
- Set
"terminal.integrated.gpuAcceleration": "off" - Open Terminal
- Type
Ctrl+randSpace - The current line disappears.
When "terminal.integrated.gpuAcceleration": "auto", this issue doesn't occur.
https://user-images.githubusercontent.com/10665499/188245201-6a1fc52c-d6dd-4276-82c4-c12d201716b0.mov
Same here but on linux and using ZSH for integrated terminal with gpuAcceleration off. Works once gpuAcceleration is changed to on.
Ctrl+r somehow breaks as soon as I type a space.
Version: 1.71.0 Commit: 784b0177c56c607789f9638da7b6bf3230d47a8c Date: 2022-09-01T07:25:10.472Z Electron: 19.0.12 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Linux x64 5.15.0-47-generic Sandboxed: No
I can't reproduce with either of those scenarios. If you resize the terminal after ctrl+r, does the line reappear?
No. It keeps hidden.
same here.
Just tested one more thing. When setting gpuAcceleration to "canvas" it works just fine like when set to "on". Only "off" seems to trigger the problem.
@kahennig @tamuratak do you use a library for the prompt? Otherwise, what's your $PS1 set as?
I cannot reproduce the issue. Might be fixed.
Version: 1.75.0-insider (Universal) Commit: b92894493e6f971a3c71912d823e699d3a05d643 Date: 2022-12-08T05:21:16.099Z Electron: 19.1.8 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin arm64 20.6.0 Sandboxed: Yes
Hey @Tyriar, this issue might need further attention.
@tamuratak, you can help us out by closing this issue if the problem no longer exists, or adding more information.