Skip to content

Commit f53b58f

Browse files
docs: add official clink integration
1 parent 158bdaf commit f53b58f

1 file changed

Lines changed: 12 additions & 11 deletions

File tree

website/docs/installation/prompt.mdx

Lines changed: 12 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -119,17 +119,8 @@ There's no out-of-the-box support for Windows CMD when it comes to custom prompt
119119
There is however a way to do it using [Clink][clink], which at the same time supercharges
120120
your cmd experience. Follow the installation instructions and make sure you select autostart.
121121

122-
Integrating Oh My Posh with Clink is easy: create a new file called oh-my-posh.lua in your Clink
123-
scripts directory (run `clink info` inside cmd to find that file's location).
124-
125-
```lua title="oh-my-posh.lua"
126-
load(io.popen('oh-my-posh init cmd'):read("*a"))()
127-
```
128-
129-
Once added, restart cmd for the changes to take effect.
130-
131-
:::info
132-
Clink has builtin support for Oh My Posh. It allows you to set the prompt using the `clink` command.
122+
Since Clink v1.7.0, Clink has builtin support for Oh My Posh. This is the recommended way to
123+
integrate the two, as it lets Clink manage the prompt for you:
133124

134125
```bash
135126
clink config prompt use oh-my-posh
@@ -141,6 +132,16 @@ To set the configuration file, use the following command:
141132
clink set ohmyposh.theme <path>
142133
```
143134

135+
:::info
136+
If you're on an older version of Clink without builtin support, you can integrate Oh My Posh
137+
manually: create a new file called oh-my-posh.lua in your Clink scripts directory (run
138+
`clink info` inside cmd to find that file's location).
139+
140+
```lua title="oh-my-posh.lua"
141+
load(io.popen('oh-my-posh init cmd'):read("*a"))()
142+
```
143+
144+
Once added, restart cmd for the changes to take effect.
144145
:::
145146

146147
</TabItem>

0 commit comments

Comments
 (0)