-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
Escape sequences (TERM?) for Nushell errors are not handled correctly #1828
Comments
should probably just enable this by default |
In #1026 (comment) |
Fancy-ANSI converts ANSI sequences to HTML. They list a couple other libraries that do the same. Might be nice in the long run. |
found the solution in nushell/nushell#11847 nu need to be called with -l nushell/nushell#11847 (comment) a pr is also coming with a script solution. nushell/nushell#11494 |
Server Info (please complete the following information):
Installation Method:
--insecure
flag at installAgent Info (please complete the following information):
Describe the bug
When running a Nushell command, the output is nice. If there's an error, the escape sequences in the error are shown and the output looks horrible.
To Reproduce
Steps to reproduce the behavior:
Note: I may be able to fix this but it will take a few months before I get to it.
Expected behavior
I expect the escape sequences to be displayed correctly and get a nicely formatted error message.
Screenshots
Here's the text version of the same.
Additional context
Here's an example Nu script.
The text was updated successfully, but these errors were encountered: