Edit is hard to use in Windows containers, now using vim as default text editor

Nobody has claimed this yet.

Edit is hard to use in Windows containers, now using vim as default text editor.

Actually I was kind of charmed that edit had made it to the new world of 64 bits like now a days.

Now I want to use it in Windows Containers but it standard adds the characters: "c0c " on the first line.
And when scrolling down it jumps the menu 1 character per line to the right.
This is very annoying and makes it almost not usable inside Containers.
From nostalgia point of view it would be nice to have something from back in the good old days still present.
Now adays I work much more in the command line world.

To every time needing to remove the characters on line 1, makes it unworkable for me.
It is a pitty to have move to vim as a Senior Windows DevOps Engineer, but yeah vim just works.

Is someone eagerly motivated enough to make the "edit" tool more environment proof? And also make it work properly inside the Windows containers?
I wish I was skilled enough to make a quick fix in the code, but I am not there yet.
Maybe someone would like to collaborate?

Start by reproducing issue #874 in a Windows container using the edit tool and capture the terminal, encoding, and container details that produce the extra characters and scrolling offset. Read the relevant terminal-rendering and input-handling entry points once the failure is localized. Done means edit opens and scrolls correctly in the reported Windows container scenario without requiring vim or manual removal of characters.

Written by the indexing model from the issue text.