Customize
The standard initialization sets Oh My Posh' default theme. This configuration is downloaded and kept up-to-date with Oh My Posh' version every time the shell starts.
To set a new config/theme you need
to change the --config option of the oh-my-posh init <shell> line in your profile or .<shell>rc script
(see prompt) and point it to the location of a predefined theme or custom configuration.
There are two possible values the --config flag can handle:
- a path to a local configuration file
oh-my-posh init pwsh --config 'C:/Users/Posh/jandedobbeleer.omp.json' | Invoke-Expression
- a URL pointing to a remote config
oh-my-posh init pwsh --config 'https://raw.githubusercontent.com/JanDeDobbeleer/oh-my-posh/main/themes/jandedobbeleer.omp.json' | Invoke-Expression
Get inspiration
The Windows and homebrew installers also bundle the predefined configurations (themes). You can use the following way to reference them directly. This will keep them up-to-date and compatible with future updates.
- windows
- homebrew
For example, to use the jandedobbeleer theme, alter the init line like this (powershell):
oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/jandedobbeleer.omp.json" | Invoke-Expression
When using homebrew, all themes are installed alongside Oh My Posh in $(brew --prefix oh-my-posh)/themes.
To use any of the themes, use the following syntax (zsh):
eval "$(oh-my-posh init zsh --config $(brew --prefix oh-my-posh)/themes/jandedobbeleer.omp.json)"
Config syntax
The examples below use a local path to the jandedobbeleer theme, adjust the --config value
to reflect your use-case.
- powershell
- cmd
- zsh
- bash
- fish
- nu
oh-my-posh init pwsh --config ~/jandedobbeleer.omp.json | Invoke-Expression
Once altered, reload your profile for the changes to take effect.
. $PROFILE
When the above command gives an error, make sure to create the profile first and add the oh-my-posh init above.
New-Item -Path $PROFILE -Type File -Force
load(io.popen('oh-my-posh init cmd --config C:/Users/Posh/jandedobbeleer.omp.json'):read("*a"))()
Use the full path to the config file, not the relative path. You can make use of forward slashes to avoid having to use double backslashes.
Once altered, restart cmd for the changes to take effect.
eval "$(oh-my-posh init zsh --config ~/jandedobbeleer.omp.json)"
Once altered, reload your profile for the changes to take effect.
exec zsh
eval "$(oh-my-posh init bash --config ~/jandedobbeleer.omp.json)"
Once altered, reload your profile for the changes to take effect.
exec bash
Oh My Posh requires fish v3.4.0 or higher.
oh-my-posh init fish --config ~/jandedobbeleer.omp.json | source
Once altered, reload your config for the changes to take effect.
. ~/.config/fish/config.fish
Oh My Posh requires Nushell v0.68.1 or higher.
Run the following command:
oh-my-posh init nu --config ~/jandedobbeleer.omp.json
it saves the initialization script to ~/.oh-my-posh.nu by default.
Then edit the Nushell config file ($nu.config-path) and add the following line at the bottom:
source ~/.oh-my-posh.nu
If you want to save the initialization script elsewhere, you should run a command like:
oh-my-posh init nu --config ~/jandedobbeleer.omp.json --print | save /mylocation/myscript.nu
and add the source line like:
source /mylocation/myscript.nu
Once altered, restart Nushell for the changes to take effect.
For the time being, there is a problem with the initialization using Oh My Posh installed via Homebrew.
To resolve this, you can use the --strict flag which tells Oh My Posh to use the executable name and not the
full path in the initialization. For example:
oh-my-posh init nu --config ~/jandedobbeleer.omp.json --print --strict | save /mylocation/myscript.nu
This way for a new Oh My Posh version that does not update the initialization script, you don't have to recreate a new one.
When using oh-my-posh in Windows and the WSL, know that you can share your theme with the WSL by pointing to a theme in your Windows user's home folder.
Inside the WSL, you can find your Windows user's home folder here: /mnt/c/Users/<WINDOWSUSERNAME>.
Adjust a theme
Maybe there's a theme you like, but you don't fancy the colors. Or, maybe there's a segment you want to tweak/add, or replace some of the icons with a different one. Whatever the case, read through available options first, by starting with the configuration guide.
You can export the current theme (default, or set via --config) to the format you like (json, yaml, or toml)
which can be used to tweak and store as your own custom theme.
oh-my-posh config export --output ~/.mytheme.omp.json
Be careful not to adjust the theme files in their original location as they're updated together with Oh My Posh which will remove your customizations. Always copy, or export them and save the new configuration outside of the Oh My Posh internal themes folder.
Read the docs
To fully understand how to customize a theme, read through the documentation in the configuration and segments sections. The configuration section covers the basic building blocks and concepts of Oh My Posh themes, while the segments section covers how to configure each available segment.