mudhorn/oh-my-posh
1
0
Fork 0
mirror of https://github.com/JanDeDobbeleer/oh-my-posh.git synced 2024-11-09 20:44:03 -08:00
Code Issues Actions 3 Packages Projects Releases Wiki Activity

docs(faq): fix grammar and typos

Browse source
This commit is contained in:
edwin-shdw 2024-07-09 08:55:19 +02:00 committed by Jan De Dobbeleer
parent 3d0c85b211
commit d6ee191140
1 changed files with 3 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/docs/faq.mdx
View file

@ -20,7 +20,7 @@ oh-my-posh init pwsh --config ~/custom.omp.json | Invoke-Expression
```
:::warning
Forcing the entire session to UTF8 can have unwanted side-effects for other executables. We can't be held liable for that,
Forcing the entire session to UTF8 can have unwanted side effects for other executables. We can't be held liable for that,
consider this a temporary workaround until the original PowerShell [issue][pwsh-20733] is resolved.
:::
@ -235,7 +235,7 @@ The issue is that PowerShell on Windows doesn't yet default to UTF-8. Resolve th
If the location contains non-ASCII characters, non-UTF-8 PowerShell may provide a wrong path to Oh My Posh, which can break the initialization.
The scenario for non-ASCII location:
- Your computer has a non-ASCII user name.
- Your computer has a non-ASCII username.
- Your [config file](./installation/customize.mdx) is under your `$HOME`.
:::
@ -262,7 +262,7 @@ $OutputEncoding = [console]::InputEncoding = [console]::OutputEncoding = New-Obj
### 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`.
You can fix this by adding the right configuration to `~/.zshrc`.
```bash
HISTFILE=~/.zsh_history