Closed burhan closed 2 years ago
Hey @burhan - in the erroneous case, what font is your Console using?
The same font, I haven't changed the console settings.
On Thu, Aug 30, 2018, 7:07 PM Rich Turner notifications@github.com wrote:
Hey @burhan https://github.com/burhan - in the erroneous case, what font is your Console using?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Microsoft/console/issues/243#issuecomment-417374775, or mute the thread https://github.com/notifications/unsubscribe-auth/AAkz6NeU-xqShgtZjZOl1GmeVvQlVKwNks5uWA3BgaJpZM4WTCRS .
--
-- Burhan Khalid Sent from a mobile device
Are you sure that the font is still installed?
It's possible that the Ubuntu app got updated - I don't believe that should change the console settings, but it might have. Can you post a screenshot of the font dialog?
None of those updates should have anything to do with conhost, so there must be something else at work here.
@Burhan: And do you have a link to the font you're using? Is it this one?
The font is installed as per the properties window.
The font installed is the same one as in your link @bitcrazed
I am not sure if this is related, but in VS code, the font renders correctly
In cmd.exe
properties, the font shows and its used by default correctly:
Could you share your zsh configuration declaring the color chevrons?
i.e. echo $PROMPT
${SSH_TTY:+"%F{9}%n%f%F{7}@%f%F{3}%m%f "}%F{4}${_prompt_sorin_pwd}%(!. %B%F{1}#%f%b.)${editor_info[keymap]}
And what does your .~/zshrc
look like?
And any other steps you took to configure your prompt to use that theme would be useful. Difficult to diagnose unless we can repro.
I am using Prezto, and the .zshrc
is pretty stock:
burhan@xps:~$ cat ~/.zshrc
#
# Executes commands at the start of an interactive session.
#
# Authors:
# Sorin Ionescu <sorin.ionescu@gmail.com>
#
# Source Prezto.
if [[ -s "${ZDOTDIR:-$HOME}/.zprezto/init.zsh" ]]; then
source "${ZDOTDIR:-$HOME}/.zprezto/init.zsh"
fi
# Customize to your needs...
# enable color support of ls and also add handy aliases
if [ -x /usr/bin/dircolors ]; then
test -r ~/.dircolors && eval "$(dircolors -b ~/.dircolors)" || eval "$(dircolors -b)"
alias ls='ls --color=auto'
alias dir='dir --color=auto'
#alias vdir='vdir --color=auto'
alias grep='grep --color=auto'
alias fgrep='fgrep --color=auto'
alias egrep='egrep --color=auto'
fi
export PYENV_ROOT="$HOME/.pyenv"
export PATH="$PYENV_ROOT/bin:$PATH"
eval "$(pyenv init -)"
export PATH="$HOME/.rbenv/bin:$PATH"
eval "$(rbenv init -)"
export PATH="$HOME/.rbenv/plugins/ruby-build/bin:$PATH"
Here is the Prezto configuration (the customized parts, removed the commented parts for brevity):
zstyle ':prezto:*:*' color 'yes'
zstyle ':prezto:load' pmodule \
'environment' \
'terminal' \
'editor' \
'history' \
'directory' \
'spectrum' \
'git' \
'utility' \
'completion' \
'syntax-highlighting' \
'history-substring-search' \
'prompt'
zstyle ':prezto:module:autosuggestions:color' found ''
zstyle ':prezto:module:completion:*:hosts' etc-host-ignores \
'0.0.0.0' '127.0.0.1'
zstyle ':prezto:module:editor' key-bindings 'vi'
zstyle ':prezto:module:editor' dot-expansion 'yes'
zstyle ':prezto:module:history-substring-search:color' found ''
zstyle ':prezto:module:history-substring-search:color' not-found ''
zstyle ':prezto:module:history-substring-search' globbing-flags ''
zstyle ':prezto:module:prompt' theme 'sorin'
zstyle ':prezto:module:syntax-highlighting' highlighters \
'main' \
'brackets' \
'pattern' \
'line' \
'cursor' \
'root'
zstyle ':prezto:module:syntax-highlighting' pattern \
'rm*-rf*' 'fg=white,bold,bg=red'
zstyle ':prezto:module:terminal' auto-title 'yes'
zstyle ':prezto:module:terminal:multiplexer-title' format '%s'
Deja Vu seems not cover these angle brackets and Console need to support font fallback to display them. Therefore, Get rid of GDI ASAP please!
@burhan, The fonts in provided VS Code and cmd.exe screenshots look different to the naked eye. While the one in cmd.exe definitely looks like Ubuntu Mono, the VS Code one most certainly doesn't.
I wonder if this is the same problem as #3257? There's a lot more discussion there and a potential workaround, selecting "Install for all users" on the font may get it working properly.
Hey so this was filed like, four years ago, and obviously there's been a lot of work done since then. Is this still happening? I think we added some better support for unsupported glyphs in the console in the latest Win11 bits. Then there's also the Terminal, which may have never had this issue at all. We never did nail down a specific repro for this one, so maybe it's gone/?
This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.
I am on Windows 10 Pro 1803 (17134.228) on a Dell XPS 15 9570 with the 4K screen (not sure if this matters).
I have been using "Ubuntu mono derivative Powerline" without issues on WSL. Yesterday I noticed that my zsh prompt no longer renders the font correctly; it now shows empty boxes instead of >>> (three arrows).
Here is what it used to look like:
I'm really not sure what triggered this; here is my Windows Update log: