VM instance SSH connection produce unreadable characters(windows google cloud shell)

[GoogleCodeExporter]

What steps will reproduce the problem?
VM instance SSH connection produce unreadable characters(windows google cloud 
shell)

What is the expected output? What do you see instead?
SSH Login to VM instance using google cloud shell and then list the files.I'm 
getting the below output.

←]0;Arul@instance-a: ~Arul@instance-a:~$ ls
←[0m←[01;34mejabberd-2.1.13←[0m  ←[01;31mejabberd-2.1.13.tgz←[0m
←]0;Arul@instance-a: ~Arul@instance-a:~$ cd ..
←]0;Arul@instance-a: /homeArul@instance-a:/home$ cd ..
←]0;Arul@instance-a: /Arul@instance-a:/$ ls
←[0m←[01;34mbin←[0m   ←[01;34metc←[0m         ←[01;34mlib←[0m    
←[01;34mmnt←[0m   ←[01;34mroot←[0m  ←[01;34mselinux←[0m
  ←[01;34msys←[0m  ←[01;34mvar←[0m
←[01;34mboot←[0m  ←[01;34mhome←[0m        ←[01;34mlib64←[0m  
←[01;34mopt←[0m   ←[01;34mrun←[0m   ←[01;34mshare←[0m    ←[
30;42mtmp←[0m  ←[01;36mvmlinuz←[0m
←[01;34mdev←[0m   ←[01;36minitrd.img←[0m  ←[01;34mmedia←[0m  
←[01;34mproc←[0m  ←[01;34msbin←[0m  ←[01;34msrv←[0m      ←[
01;34musr←[0m
←]0;Arul@instance-a: /Arul@instance-a:/$

What is the output of 'gcloud version'?
1.16.1

Please provide any additional information below.

Original issue reported on code.google.com by ad...@chitchatto.com on 7 Jul 2014 at 2:45

Attachments:

• gutil_prob.jpg

[GoogleCodeExporter]

hi,
Any idea about this problem.. Can you please let me know as soon as possible.. 
pls guys.... we are working in a very serious project..

Thanks in advance :)

Original comment by ad...@chitchatto.com on 10 Jul 2014 at 5:13

[GoogleCodeExporter]

Thanks for the report!  We're looking into it.

Original comment by jeffvaug...@google.com on 12 Aug 2014 at 8:24

• Changed state: Accepted

[GoogleCodeExporter]

It looks the `ls` is returning ANSI escape sequences to change the color of 
it's output.

Unfortunately cmd.exe doesn't understand ANSI color so you're getting a textual 
representation of the escape sequences instead of the color change.

You might consider using an alternate shell, or ensuring that `ls` doesn't 
return colorized output.   (If you run `alias` do you see `alias ls='ls 
color=auto'`?  If so removing this alias may due the trick.)

Original comment by jeffvaug...@google.com on 12 Aug 2014 at 8:34

• Changed state: WorkingAsIntended