Edit produces documents with no LF/CRLF after the last line · Issue #41 · microsoft/edit
github.com
I feel like ensuring the presence of a final EOL is something a text editor is supposed to do.

The comment does well in providing context and arguments.

Lets go back to the closest thing we have for requirements for this editor…Default CLI Editor - Feature Exploration!. This discussion was based on the current state of windows and was not concerned with UNIX.

Being a simple text editor, it should not hallucinate, it should not add text one did not type, it should not change the text that was typed. If the user typed a tab character, it was because the user wanted a tab character. If you want four spaces then type four spaces.

edit should by default work like the original namesake and not hallucinate or add characters that were not typed or make assumptions.

Where do you draw the line on “smart” features? Tab should not add indent spaces? Encoding or newline mechanisms? Determining EOF newline?

  • Kissaki@programming.devOPEnglish
    6·
    5 days ago

    Given the announcement of edit replacing the old 32-bit MS-DOS edit.com with minimal footprint, I was surprised Microsoft considered multi-platform to even be in-scope.

    I guess, given it’s Rust, it was simple to say “sure, why not”. But this ticket shows that you automatically have to discuss and handle multi-platform questions that arise.