Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

actual PowerShell have alredy coloring itself #50

Open
theuserbl opened this issue Jul 6, 2022 · 1 comment
Open

actual PowerShell have alredy coloring itself #50

theuserbl opened this issue Jul 6, 2022 · 1 comment

Comments

@theuserbl
Copy link
Contributor

I have had used PowerShell 7.1.4 before. And that have no coloring of Get-ChildItem.

But now I have tried out the actual PowerShell 7.3.0-preview.5. And that have a coloring for the exe-files, the directories, *.zip files, ps1 files, psm1 files, psd1 files and possible other.

dll files, txt files, etc. are there non colored. Who that wants needing possibly still Get-ChildItemColor. But for all other is coloring in the original Get-ChildItem already included.

@theuserbl
Copy link
Contributor Author

I currently see, that the coloring of Get-ChildItem is much bader then that of Get-ChildItemColor.
Get-ChildItem uses now the ANSI escape code.
That ends up, that a dir | ogv have the directory "Downloads" listed as "[44;1mDownloads[0m".
Similar with all colored files.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant