microsoft / microsoft/terminal

Japanese character output in Integrated Terminal of Visual Studio Code causes the next prompt out of position after upgrading to Creators Update

Open
#118 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Area-Output Issue-Bug Product-Conhost
Dominant language
C++
Stars
105k
Forks
9.6k
Avg merge
3d 17h
Merged PRs (30d)
29

Description

From @yusuke-konishi on April 10, 2017 3:50

  • A brief description

Japanese character output in Integrated Terminal of Visual Studio Code causes the next prompt out of position after upgrading to Creators Update. This issue is reproducible 100%.

For example, echo あ causes the next prompt out of position. The screenshot below is the result of ls -la with en only, and echo あ. ls -la does not cause any problem, but echo あ causes the next prompt out of position.

ls_en_echo

  • Expected results

Japanese character output in Integrated Terminal of Visual Studio Code keeps the next prompt in the correct position.

  • Actual results (with terminal output if applicable)

Japanese character output in Integrated Terminal of Visual Studio Code causes the next prompt out of position.

  • Your Windows build number

Version 1703, build 15063.13 (Japanese)

  • Steps / All commands required to reproduce the error from a brand new installation
  1. Install Windows 10 Creators Update
  2. Install BoW on Creators Update
  3. Install Visual Studio Code (v1.11.1)
  4. Open BoW in Integrated Terminal by [Ctrl] +[@]
  5. Run echo あ
    -> This causes the next prompt out of position.
  • Other troubleshooting

I tried repro on the following three environment by Visual Studio Code v1.11.1. By this results, this does not seem to depend on Visual Studio Code, but Creators Update. Can't BoW handle this issue?

  1. OK
    OS: build 14393.0
    BoW: Ubuntu 14.04

  2. NG
    OS: build 15063.13 (upgraded from build 14393.0)
    BoW: Ubuntu 14.04 (not upgraded)

  3. NG
    OS: build 15063.13
    BoW: Ubuntu 16.04

Copied from original issue: Microsoft/WSL#1871

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in the Integrated Terminal with BoW on Windows 10 build 15063.13, running echo あ after the listed installation steps, and compare it with build 14393. No source file or test is named; done means the next prompt remains correctly positioned after Japanese output, including the reported Creators Update environments.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp, vscode
Domain
cli, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.