This is most probably a problem with your $PS1 variable. The $PS1 variable is defined in your zshrc file. This file is located in /etc/zshrc
The $PS1 variable stores the encoded (ASCII I believe) information to produce your prompt.
The first thing you want to do is see what your $PS1 is currently. To do this type echo $PS1 in your terminal. The standard prompt for Debian 8 ZSH is %m%#, which equates to hostname% or whatever your hostname happens to be(my prompt is localhost%). Most likely, the reason for your odd terminal prompt is a messed up $PS1 variable, so to change it back to the default Debian 8 ZSH prompt type PS1="%m%#" in your terminal... keep in mind that this is temporary and your prompt will be reset every time you exit the terminal. To make this change permanent open your /etc/zshrc file and append
PS1="%m%#"
to the file. Type exit to close the terminal, and then open it up again. The new, fixed terminal prompt should be displayed.
On a side note
These instructions are for ZSH, not bash! The default prompt for bash in Debian 8 is \u@\H: \w $ which equates to username@hostname: ~ $ (If I was in the /bin directory, my prompt would look like bradleysadowsky@localhost: /bin $). The characters in a ZSH prompt are very different from the characters in the bash prompt. Bash has characters ZSH does not and vice versa. Another key difference is (mostly) in bash, the special $PS1 characters start with a backslash(\), whereas in ZSH (mostly), the special $PS1 characters start with a percent symbol(%) For a good list of the more useful ZSH escape characters go to this webpage. For a comprehensive guide to the $PS1 variable in bash and some escape characters for bash, go to this webpage.
Finally
To set up your own prompt just put those escape characters together in a way you like, and edit your /etc/zshrc adding your prompt to it. A good prompt that is useful and beautiful for ZSH is [%n@%m] %~> which is equivalent to [username@hostname] ~>, so for me (if I was in /bin) [bradleysadowsky@localhost] /bin>.
.zshrcand any other relevant file) to reproduce the problem — basically we need to see your prompt setting. Also tell us the output oflocale. – Gilles 'SO- stop being evil' Jun 24 '15 at 22:39$TERMhas no effect on what the terminal emulator can do — see Why xterm displays 256 colors (not xterm-256color)? – G-Man Says 'Reinstate Monica' Jun 25 '15 at 02:35