Embedded console regressions

[Grimelios]

using System;
using System.Threading;

namespace MyNamespace
{
    static
    {
        public static void Main()
        {
            // Arbitrarily large value that guarantees that printed output will extend past the bottom of the embedded console.
            for (let i < 10'000)
            {
                Console.WriteLine(scope $"Line {i}: this is a long string, long enough to trigger text wrapping functionality within the IDE's embedded console. Unfortunately, text wrapping appears to be dysfunctional at this time.");

                // Adjust if you'd like to reach the bottom of the embedded console faster.
                Thread.Sleep(500);
            }
        }
    }
}

Tested on nightly 05/18/2026. I've identified two problems with the IDE's embedded console (Preferences -> Settings -> Console -> Debug Console -> Embedded). I believe these are regressions, although I don't know precisely which release caused them.

1. Text wrapping no longer respects the console window's width. For example, here's a screenshot using a narrow console window showing how most of the long string is cut off. Some quick experimentation indicates that text is wrapped at 120 characters regardless of the console's width.

2. The embedded console no longer auto-scrolls to ensure that printed output remains visible. The behavior here is odd: the console does eventually begin auto-scrolling, but it lags behind by about 33 lines. In the image below, note how the console indicates Ln 134 despite "Line 101" being the last visible output.

[bfiete]

Not sure how this could have changed recently... these are all the files related to the console, and none have changed since 2024
https://github.com/beefytech/Beef/commits/master/IDE/src/ui/ConsolePanel.bf
https://github.com/beefytech/Beef/commits/master/IDE/src/util/ConsoleProvider.bf
https://github.com/beefytech/Beef/commits/master/BeefTools/BeefCon/src/Program.bf‎

If you could test out a few builds, maybe do a little binary search to find where it started failing, that would be nice... or at least go back to something like this just to verify it actually has changed:
https://nightly.beeflang.org/BeefSetup_0_43_6__12_01_2025.exe

Date format at the end is MM_DD_YYYY if that wasn't apparent... there's a lot of builds archived so you can just put dates in there to check...

[Grimelios]

Well, I'm a little baffled. From checking prior versions (all the way back to the stable release from March 2025), seems like the console's behavior has NOT changed in recent memory. Either my memory is disturbingly faulty or there's some other root cause, although I have no idea how that'd be possible.

In any case, labeling these issues as regressions was an error, and I apologize. The problems themselves (incorrect text wrapping + auto-scroll) still remain, so I'll leave this issue open unless additional information comes to light.

[bfiete]

I tried your wrapping example and it works perfectly for me. No issues.

With the "Line XXX" test, I've noticed that there appears to be a race condition for what the last visible line is with a fast-running program, but if I add a sleep at the end of the program then it always shows the proper position.

[Grimelios]

Bizarre. My desktop is running Windows 10, but I've additionally verified these problems on my laptop, which is running Windows 11. Clearly there's a root cause separate from Beef. I'll leave it up to you to close this issue if you'd like, or it can remain open so that I can comment with a solution if I find one. Thank you.

[aharabada]

I tried it as well, and it appears that the text wrapping is somehow affected by the UI scaling configured in Windows?

100% Scaling:

150% Scaling:

Edit: Oh yeah, and extending the console after stopping the program seems to be doing... interesting things:

Original width:

Extending the console:

[Grimelios]

Seconding the strange formatting after extending the console. As for UI scaling, mine is set to 100%, but I'm still not wrapping correctly.