You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's great that Set-PSReadlineOption -Colors supports ANSI escape codes on Unix systems. However, it could support them better. These codes support more than just colors.
For example, my Paramter color setting is:
`e[2;3;255;102m
This sets not just color, but also makes the parameter italic. Unfortunatly, PSReadLine doesn't clear formatting between words, so every word after that parameter it also in italics.
The workaround is to put the Clear Formatting escape code (`e[0m) at the start of every single symbol type's color setting, which also means I have to use ANSI for every color setting.
A better solution would be for PSReadLine to automatically write `e[0m between words on Unix systems.
The text was updated successfully, but these errors were encountered:
It's great that
Set-PSReadlineOption -Colors
supports ANSI escape codes on Unix systems. However, it could support them better. These codes support more than just colors.For example, my Paramter color setting is:
This sets not just color, but also makes the parameter italic. Unfortunatly, PSReadLine doesn't clear formatting between words, so every word after that parameter it also in italics.
The workaround is to put the Clear Formatting escape code (`e[0m) at the start of every single symbol type's color setting, which also means I have to use ANSI for every color setting.
A better solution would be for PSReadLine to automatically write `e[0m between words on Unix systems.
The text was updated successfully, but these errors were encountered: