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

Funky output when using VS Code or Windows Terminal #32

Open
Tdue21 opened this issue Feb 19, 2025 · 3 comments
Open

Funky output when using VS Code or Windows Terminal #32

Tdue21 opened this issue Feb 19, 2025 · 3 comments

Comments

@Tdue21
Copy link

Tdue21 commented Feb 19, 2025

I am using this for ad-hoc cs-script ... scripts in VS Code, and it works like a charm.
However, the output itself is a bit funky:

Image

Any ideas as to make it look like it should in VS Code?

Also, I tried calling the script directly in Windows Terminal, where the output is almost correct, except for the corners.

Image

I get that it is probably something I just have to live with, but if there is an easy fix, I'd love to hear it :)

@MoaidHathot
Copy link
Owner

Thanks @Tdue21 for creating the issue. Could you please provide more information?
In both VsCode's and Windows Terminal, which shell are you using? CMD/PowerShell Core/PowerShell Windows/etc... ?

@Tdue21
Copy link
Author

Tdue21 commented Feb 23, 2025

PowerShell 7.4 or 7.5, I forget right now which.
In Windows Terminal it is the same whether it is PowerShell or Cmd.
I'll add more when I am at my PC.

@Tdue21
Copy link
Author

Tdue21 commented Feb 24, 2025

Ok, funny thing. If I run my code in VS Code, with Ctrl+Alt+N I get this:
Image

But, if I run it in the integrated terminal, I get this:
Image

And now it also looks fine in Windows Terminal:
Image

I did rename the script file from .cs to .csx, but I don't see how that can affect the output. Only thing it should affect is how VS Code attempts to execute it when using the Ctrl+Alt+N command, which it didn't by the way ;)

So, it would appear that I was just being unlucky when I tried the first time *shrug*

Only the Output window in VS Code seem to be affected, and that is most likely some kind of encoding thing.

I don't think it is something worth spending a lot of time on.

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

2 participants