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

[martijnvandenboom]

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?

[lhecker]

Sorry about the bad experience. I'm still very happy to hear that another person kind of liked this little fun project. I hope to spend more time on it in the future to make it even better.

Your issue is a dupe of #109. (You should've found it easily had you simply searched for "c0c", so I'm softly scolding you now. *bonk*!)

I have some ideas about the c0c thing. But more than anything, I'm curious about how you experience it with Windows Containers. They're fairly new so I haven't had time to play with them personally yet. I assume you're not using SSH to connect to them, right? Or are you? Because all of the "c0c" issues so far were about SSH and it had a very specific reason.

[DHowett]

@lhecker I'd say... Windows Server 2025 or GE+ and "old ConPTY" ;)

[ingvdboom]

Sorry about the bad experience. I'm still very happy to hear that another person kind of liked this little fun project. I hope to spend more time on it in the future to make it even better.

Your issue is a dupe of #109. (You should've found it easily had you simply searched for "c0c", so I'm softly scolding you now. bonk!)

I have some ideas about the c0c thing. But more than anything, I'm curious about how you experience it with Windows Containers. They're fairly new so I haven't had time to play with them personally yet. I assume you're not using SSH to connect to them, right? Or are you? Because all of the "c0c" issues so far were about SSH and it had a very specific reason.

I am into nostalgia as I appreciate the good old days and like to see something that will kind of stand the test of time. I am eager to know if the old code is being reused or that it is a completely new project?

You were right about it being kind of duplicate as I saw the ticket 109 (for me not an easy find) you mentioned, but I also see some uniqueness in my ticket considering it has not exactly what I am seeing. So thanks for mentioning. And I think my approach is different running it in containers.

I don't use SSH by the way. I have a Docker file (see attached zip file). and build and run with the following commands as administrator:

WinGet_Windows_Server_2025_-_20260611_1259.zip

$ docker build --isolation=process -t my-windows-app:latest .
$ docker run -it --isolation=process my-windows-app:latest

This way it gives me the prompt of inside my container in my Terminal app.
And then edit behaves such as in the screenshot.

1. It adds the strange characters c0c on the first line and wants to save them on exit.
2. As I scroll down in the file it moves the total screen menu one character to the right, quite annoying.

As I said for now I am installing VIM everywhere, it just works.

Hope to see more of this come to a nice little convenient cross platform editing tool.
It brings back so many good memories.

It brings back memories to my late uncle who I helped out with startup *.bat files that presented a menu to start his applications. It needed altering every now and then and I reused the structure for other people including myself to make nice menus.

And I remember doing the editing of autoexec.bat and config.sys in the MS DOS glory days. Like adding himem.sys settings to improve the memory available. :)

[ingvdboom]

@lhecker I'd say... Windows Server 2025 or GE+ and "old ConPTY" ;)

I am not sure what you mean to say. Maybe you want to clarify to me the point you are trying to make?

Am I understanding this correctly that maybe Microsoft needs to make the fix in ConPTY?
So that edit will work when ConPTY will stop injecting garbage characters?

[lhecker]

The "@lhecker" in that comment means that it was directed to the user "lhecker". I'm lhecker.

That lhecker person will investigate this.

[DHowett]

Hah! But it's a fair question. Leonard was asking how the original filer "experienced" the issue outside of using SSH and the one known cause. I think that most folks using Containers are on Windows Server 2025 or Client 25H1; the in-box version of ConPTY there might mangle report responses. It's not supposed to, but... you know. Bugs, bugs.

We're looking for the right way to service bug fixes for things like that.

[ingvdboom]

I want to add that I was working inside a ltsc2022 version of the Windows Server Docker container when this happened. Not thinking yet of trying it inside a ltsc2025 version. Now I did. And it seems to work properly now in the Windows Server 2025 Docker container.
I think that by the end of this year when 2022 is put in EOL status I can slowly start to revert back from VIM to Edit. So cool.

[lhecker]

Do you have any instructions for me to reproduce this issue with ltsc2022 (some concrete step-by-step instructions)?

[ingvdboom]

Do you have any instructions for me to reproduce this issue with ltsc2022 (some concrete step-by-step instructions)?

@lhecker
Sure, read my previous message.
I have included the zip file that creates the Docker container.
Unpack.
Go to the directory.
Inside run with administrator rights:

$ docker build --isolation=process -t my-windows-app:latest .
$ docker run -it --isolation=process my-windows-app:latest

It can take some time. Please be patient.

For me it took: Build finished in 40m 5.9s