Skip to main content

FAQ

Before validating anything, make sure you're on the latest version of Oh My Posh and your terminal and shell are up-to-date.

The prompt is slow (delay in showing the prompt between commands)​

Windows

Make sure Windows Defender, or your AntiVirus, has an exclusion configured.

You can use the oh-my-posh debug functionality to see where Oh My Posh spends its time. In case there's no clear culprit (timings indicate everything's OK), chances are some modules are the culprit. We bootstrap a few PowerShell modules to maximise compatibility, but sometimes these can introduce unwanted side-effects.

The modules we support are:

  • posh-git

If only your Git repo paths are slow, then try running git gc to clean up and optimize the local repository.

If nothing seems to resolve the issue, feel free to create an issue.

There are rectangles instead of icons in my prompt​

The font you're using doesn't have the needed standard extended glyph set like Nerd Font does. Windows Terminal ships with Cascadia Code by default which has a powerline patched variant called Cascadia Code PL, but also that one misses certain interesting icons. You can fall back to any theme with the .minimal indication, or make use of a Nerd Font. Have a look at the font section for more context in case you're using all the right conditions.

Text decoration styles like bold and dimmed don't work​

The text decoration styles are based on your terminal emulator's capabilities.

A quick way to check if your terminal supports a specific style escape sequence is to take a look at the terminfo database, on Linux. Refer this page on ArchWiki.

If you are on Windows, use Windows Terminal. It closely copies the xterm-256color capabilities. See the PowerShell docs on terminal support and this GitHub comment.

Windows Terminal: Unexpected space between segments/text​

Windows Terminal has some issues with rendering certain glyphs. These issues are on their backlog. A temporary workaround is to use an invisible character at the end (\u2800).

{
"type": "executiontime",
/* other attributes here */
"properties": {
"always_enabled": true,
"template": "\ufbab\u2800" // invisible spacing character
}
}

Jetbrains terminals: Icons do not render​

They need to work on their terminal, somehow it only supports UTF-8 and not UTF-16. An issue is available for a follow-up here.

Strange colouring after exiting VIM or when using the PowerShell progress bootstrap​

This bug is caused by Windows Terminal and/or VIM. There are two issues for this, one at Windows Terminal and one at VIM.

Conda: environment name displayed in front of the prompt​

Conda will automatically prepend the prompt with the name of the environment you're in. To solely rely on Oh My Posh to set the prompt, you can configure the following setting to hide it:

conda config --set changeps1 False

Python venv: Prompt changes on activating virtual environment​

Virtual environments created with venv add the active environment's name to the prompt automatically. To disable this behaviour, set VIRTUAL_ENV_DISABLE_PROMPT environment variable to 1 on your system. Example files:

Note: Tilde (~) in paths refers to your user's home directory.

# Your PowerShell $PROFILE
$env:VIRTUAL_ENV_DISABLE_PROMPT=1

PowerShell: The term 'Set-Theme' is not recognized as the name of a cmdlet, function, script file, or operable program.​

You need to migrate using the following guide.

PowerShell: Running in ConstrainedLanguage mode​

You're here because you've seen the following message:

[WARNING] ConstrainedLanguage mode detected, unable to set console to UTF-8.
When using PowerShell in ConstrainedLanguage mode, please set the
console mode manually to UTF-8. See here for more information:
https://ohmyposh.dev/docs/faq#powershell-running-in-constrainedlanguage-mode

When running PowerShell in ConstrainedLanguage mode, we can't set the console to UTF-8. This will cause the prompt to be rendered incorrectly. There's a few options to set the console to UTF-8 from an OS perspective on Windows, other systems shouldn't be impacted.

To remove the message after manual configuration, you can add the following to your $PROFILE before importing Oh My Posh:

$env:POSH_CONSTRAINED_LANGUAGE = 1

PowerShell: The term '.../oh-my-posh.exe' is not recognized as a name of a cmdlet...​

For example:

&: The term 'C:/Users/TommiGrβ”œβ•’nlund/.oh-my-posh/oh-my-posh.exe' is not recognized as a name of a cmdlet, function, script file, or executable program.
Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

The issue is that PowerShell on Windows doesn't yet default to UTF8. Resolve the issue by adding the following line to the top of your $PROFILE:

$OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = New-Object System.Text.UTF8Encoding

Zsh: No command history (Ctrl+R does not work)​

This issue occurs when you're using plain zsh in combination with Oh My Posh. You fix this by can adding the right configuration to ~/.zshrc.

HISTFILE=~/.zsh_history
HISTSIZE=10000
SAVEHIST=10000
setopt appendhistory

Fish: $(...) is not supported​

You should update fish to v3.4.0 or higher. Fish supports $(...) and "$(...)" since v3.4.0, as described in its changelog.