Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

terminal appearance - text input has white background a #68848

Closed
BurakAy opened this issue Feb 16, 2019 · 4 comments
Closed

terminal appearance - text input has white background a #68848

BurakAy opened this issue Feb 16, 2019 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@BurakAy
Copy link

BurakAy commented Feb 16, 2019

When terminal opens the screen in blank due to text area having multiple new lines, must scroll up to see terminal has initialized . No visible cursor and first character input appears to be in middle of blank space. The issue appears to be intermittent, sometimes it initializes properly, sometimes it doesn't.

first_char

However, the following issues are always present. After entering second character, background of inputted text turns white.

white_second_char

When backspace is used to delete inputted text, the white background remains up to the furthest previously inputted character. Also, after inputting the first character, if you input a white space (press spacebar) the input following the space becomes invisible/disappears.

backspace_white

VS Code version: Code 1.31.1 (1b8e830, 2019-02-12T02:20:54.427Z)
OS version: Windows_NT x64 10.0.17763

System Info
Item Value
CPUs Intel(R) Core(TM)2 Duo CPU E7400 @ 2.80GHz (2 x 2793)
GPU Status 2d_canvas: enabled
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: disabled_off
native_gpu_memory_buffers: disabled_software
rasterization: unavailable_off
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
Memory (System) 8.00GB (3.70GB free)
Process Argv
Screen Reader no
VM 0%
Extensions (22)
Extension Author (truncated) Version
html-snippets abu 0.2.1
simple-react-snippets bur 1.2.2
path-intellisense chr 1.4.2
vscode-eslint dba 1.8.0
jquerysnippets don 0.0.1
php-debug fel 1.12.6
php-intellisense fel 2.3.10
beautify Hoo 1.4.8
python ms- 2019.1.0
cpptools ms- 0.21.0
csharp ms- 1.17.1
node-debug2 ms- 1.31.3
team ms- 1.144.1
debugger-for-chrome msj 4.11.2
LiveServer rit 5.5.1
vscode-icons rob 8.1.0
sass-indented rob 1.5.1
vscode-react-native vsm 0.8.0
vscode-wakatime Wak 1.2.5
bootstrap-3-snippets wcw 0.1.0
JavaScriptSnippets xab 1.7.2
html-css-class-completion Zig 1.18.0

(2 theme extensions excluded)

ste.
@BurakAy
Copy link
Author

BurakAy commented Feb 16, 2019

Here is another image showing the appearance after a command is run. In this example I ran 'npm start'.

input

@jevenson
Copy link

Same here but its all blue!
image

@Tyriar
Copy link
Member

Tyriar commented Mar 2, 2019

This normally happens when you've tweaked cmd.exe's default colors.

/duplicate #45693

@Tyriar Tyriar closed this as completed Mar 2, 2019
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 2, 2019
@l1xnan
Copy link

l1xnan commented Mar 30, 2019

In the windows 10 v1809 environment, many third-party terminals have this problem(felixse/FluentTerminal#108 (comment)). This problem can be resolved by removing HKEY_CURRENT_USER\Console\ScreenColors in the registry.

@vscodebot vscodebot bot locked and limited conversation to collaborators Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants