<div id="readability-page-1" class="page"><div><div><a href="https://rkttu.com/?source=post_page-----58cb4793464f--------------------------------" rel="noopener ugc nofollow"><div aria-hidden="false"><img alt="Jung-Hyun Nam" src="https://miro.medium.com/v2/resize:fill:88:88/2*P1z-D515GRYQ6WaumcAxVQ.png" width="44" height="44" loading="lazy"></div></a><a href="https://blog.devgenius.io/?source=post_page-----58cb4793464f--------------------------------" rel="noopener ugc nofollow"><div aria-hidden="false"><img alt="Dev Genius" src="https://miro.medium.com/v2/resize:fill:48:48/1*CvejhRq3NYsivxILYXEdfA.jpeg" width="24" height="24" loading="lazy"></div></a></div><figure><figcaption><a href="https://github.com/JanDeDobbeleer/oh-my-posh" rel="noopener ugc nofollow" target="_blank">JanDeDobbeleer/oh-my-posh: The most customisable and low-latency cross platform/shell prompt renderer (github.com)</a></figcaption></figure>I’m a technical writer and software developer who is an avid user of both Windows, Linux (WSL), and macOS, so naturally I’m also very interested in the terminal environment, and since PowerShell 7 was first released, I’ve been using the same shell with PowerShell on multiple operating systems.Then recently, when I heard that oh-my-posh supports zsh, bash, and even cmd (yes, that cmd on Win32, although it does require a special companion!) in addition to PowerShell, I decided to create a new setup.<h2 id="a2e0">macOS zsh</h2>As we all know, starting with macOS Catalina, zsh became the default terminal instead of bash, and using zsh on macOS is now nothing new.Of course, using oh-my-zsh makes sense and is optimized. But in my case, I want to create the same experience across multiple types of terminals, so unfortunately, oh-my-zsh isn’t going to cut it.To customize the zsh shell in oh-my-posh, I added the following to my <code>.zshrc</code> file. By the way, I should mention that I installed oh-my-posh with Homebrew.<pre># for zsh autoload -Uz compinit compinitPOSH_THEMES_PATH=$(brew --prefix oh-my-posh)/themes eval "$(oh-my-posh completion zsh)" eval "$(oh-my-posh init zsh --config "$POSH_THEMES_PATH"/clean-detailed.omp.json)"</pre>Then, restart your shell and you should see it applied.<h2 id="f9b4">macOS bash</h2>Since zsh is the default shell, you’ll rarely need to use bash on macOS for any reason. However, I wanted to make sure that I could apply oh-my-posh to macOS bash for completeness.However, I couldn’t just use it out of the box, and had to tweak the bash script that oh-my-posh generates.I added the code below to my <code>.bashrc</code> file and it worked well.<pre># for bash (macOS) POSH_THEMES_PATH=$(brew --prefix oh-my-posh)/themes eval "$(oh-my-posh completion bash)" eval "$(oh-my-posh init bash --config "$POSH_THEMES_PATH"/clean-detailed.omp.json | sed 's|\[\[ -v MC_SID \]\]|[[ -n "$MC_SID" ]]|')"</pre>Then, restart your shell and you should see it applied.<h2 id="a85f">cmd.exe</h2>If you’re thinking, “cmd.exe to oh-my-posh? I can’t believe it,” you’re right. cmd.exe by itself is obviously not enough, you need to supplement it with a tool called Clink, and then you can link oh-my-posh on top of it.In this case, oh-my-posh will write a renderer based on Lua. Unfortunately, the initialization code for autocomplete is not provided for cmd.Luckily, Clink is easy to install via the WinGet package manager. Simply install it with the command below, and it will automatically attach to your existing cmd.exe to extend its functionality.<pre>winget install Clink</pre>Next, create an <code>oh-my-posh.lua</code> file in the <code>%localappdata%\Clink</code> folder and open it with your favorite text editor. There’s no convention to the filename, and Clink seems to check all the Lua scripts in that folder and import them automatically.<pre>-- for cmd load(io.popen('oh-my-posh init cmd --config ' .. os.getenv("localappdata") .. '\\Programs\\oh-my-posh\\themes\\clean-detailed.omp.json'):read("*a"))()</pre>Then, restart your shell and you should see it applied.<h2 id="0fce">Ubuntu bash</h2>Naturally, you should be able to apply oh-my-posh from the Linux bash shell or zsh shell without any problems.However, on Linux, unless you’re using Homebrew for Linux, you’ll have to install it manually. In this article, I’ll show you how to apply oh-my-posh to the bash shell on Ubuntu Linux.First, install the two required packages.<pre>sudo apt -y install unzip curl</pre>The command to install oh-my-posh is easily accessible as a one-line command.<pre>curl -s https://ohmyposh.dev/install.sh | bash -s</pre>Next, run the script below to install the theme files. This is because we are installing oh-my-posh manually, not using a package manager. We’ll create a <code>.poshthemes</code> directory under your home directory and install the theme files there.<pre>mkdir ~/.poshthemes curl -L https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/themes.zip -o ~/.poshthemes/themes.zip unzip ~/.poshthemes/themes.zip -d ~/.poshthemes chmod u+rw ~/.poshthemes/*.json rm ~/.poshthemes/themes.zip</pre>I added the code below to my <code>.profile</code> file and it worked well.<pre>eval "$(oh-my-posh completion bash)" eval "$(oh-my-posh init bash --config ~/.poshthemes/clean-detailed.omp.json)"ba</pre>Then, restart your shell and you should see it applied.<h2 id="b56f">PowerShell</h2>This section is also a bit special because PowerShell is multi-platform these days.Since PowerShell is multi-platform these days, this section is a bit special. After looking at what each platform populates in the PowerShell script pointed to by the <code>$PROFILE</code> variable, I’m going to talk about something special.Before we get started, if this is your first time configuring with the <code>$PROFILE</code> variable in PowerShell, I recommend that you start by making sure you have a directory pointed to by the <code>$PROFILE</code> variable with the command below. This is because you can’t create a file without a directory.<pre>mkdir -Path (Get-Item -Path $PROFILE).Directory.FullName -ErrorAction SilentlyContinue</pre><h2 id="a4c4">Windows, Both Built-in and Modern Version</h2>oh-my-posh can be installed with the WinGet package manager, just like any other command-line tool for Windows. You can easily install it with the command below.<pre>winget install "Oh My Posh"</pre>Next, open the profile script in your favorite text editor. If the file doesn’t exist, it will tell you to create it. After that, add the content below.<pre>$env:POSH_THEMES_PATH = Join-Path -Path (Get-Item -Path (Get-Command -Name 'oh-my-posh').Source).Directory.Parent.FullName -ChildPath 'themes' [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex</pre>Then, restart your shell and you should see it applied.<h2 id="b417">Linux</h2>On Linux, you use the same theme file to apply oh-my-posh to PowerShell for Linux as you did to apply it to the bash shell.<pre>mkdir ~/.poshthemes curl -L https://github.com/JanDeDobbeleer/oh-my-posh/releases/latest/download/themes.zip -o ~/.poshthemes/themes.zip unzip ~/.poshthemes/themes.zip -d ~/.poshthemes chmod u+rw ~/.poshthemes/*.json rm ~/.poshthemes/themes.zip</pre>Once you’ve installed the theme files, open the profile script with your favorite text editor. If the file doesn’t exist, it will tell you to create it. After that, add the content below.<pre>$env:POSH_THEMES_PATH = Join-Path -Path $Home -ChildPath '.poshthemes' [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex</pre><h2 id="6cc3">macOS</h2>For macOS, let’s assume you have oh-my-posh installed as Homebrew.Open the profile script in your favorite text editor. If the file doesn’t exist, it will tell you to create it. After that, add the content below.<pre>$env:POSH_THEMES_PATH = Join-Path -Path "$(brew --prefix oh-my-posh)" -ChildPath themes [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex</pre><h2 id="6366">Combine into a single file</h2>Remember that PowerShell runs in a single environment, albeit with some OS-specific differences, so a single script file is all you need to create an initialization script that works universally everywhere.All you need to do is check the OS version correctly, and put in some conditional statements to run the scripts you can run.You can do this by writing like below.<pre># for PowerShell (macOS) if ([Environment]::OSVersion.Platform -eq [PlatformID]::MacOSX) { $env:POSH_THEMES_PATH = Join-Path -Path "$(brew --prefix oh-my-posh)" -ChildPath themes [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex }# for PowerShell (Windows) if ([Environment]::OSVersion.Platform -eq [PlatformID]::Win32NT) { $env:POSH_THEMES_PATH = Join-Path -Path (Get-Item -Path (Get-Command -Name 'oh-my-posh').Source).Directory.Parent.FullName -ChildPath 'themes' [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex }# for PowerShell (Linux, Ubuntu) if ([Environment]::OSVersion.Platform -eq [PlatformID]::Unix) { $env:POSH_THEMES_PATH = Join-Path -Path $Home -ChildPath '.poshthemes' [scriptblock]::Create($(oh-my-posh completion powershell)).Invoke() oh-my-posh init pwsh --config "$env:POSH_THEMES_PATH/clean-detailed.omp.json" | iex }</pre><h2 id="080f">Full GIST</h2>The code we’ve seen so far has been put into a GIST. Feedback and forks are welcome.<a href="https://gist.github.com/rkttu/3d286f711ebd7de239489fc3310a80cd" rel="noopener ugc nofollow" target="_blank">How to initialize oh-my-posh with bash (macOS), bash (WSL, Ubuntu), cmd, zsh and pwsh (github.com)</a><h2 id="ab9e">Conclusion</h2>With these tips, you can ensure a consistent terminal experience regardless of the OS or terminal version. For me, this has helped me create a satisfying terminal working experience.I’ve used a clean, detailed theme for this article, but there are plenty of other themes that can be adapted, and I hope you have fun creating your own unique, OS-agnostic terminal experience with your favorite theme.</div></div>

Stories by Jung-Hyun Nam on Medium

Create an improved, consistent, OS-agnostic terminal experience with oh-my-posh
Continue reading on Dev Genius »

Use oh-my-posh everywhere

댓글