Chris wrote:

When sharing windows files there's always line ending issues.

I recommend 'dos2unix'.

But that's what the GNUWIN32 tools are for.

They already have the line ending issue solved for you.
Or at least, there are better odds of it being that way.

Then you don't need to be playing tennis with the files
to get some work done.

Solvable != Convenient, that's the problem.

And nobody is going to modify the contents of the
WSL toolset, at least without a clear picture of
what it's for. It was invented for some purpose,
something about "editing Azure instances" or the
like. Is it succeeding ? Or was this merely a bar
bet of some sort, created without a clear picture
of how to measure success ?

I've used WSL occasionally, but there are other
ways to get stuff done.

If you use the Linux "file" command, there are
at least 100 classifications for text files, and
for some of those, you cannot safely use dos2unix
and unix2dos, without damaging the files. I tried this
on a Firefox tarball, and it was a disaster if done
in a non-selective way. You have to be pretty careful,
to avoid making a mess, and it would be an all-day job
to make the files open neatly in Notepad in each case.

Line endings are not always a pleasant topic. You'll
find out when you get there :-/

And Windows 10 is partially solving some of these issues,
in that ancient stuff that "wasn't normally opened for
improvements", is seeing work. We had Command Prompt.
We got a Powershell. And there's a new Terminal thingy
that came out a few days ago, which is presumably an
attempt at a replacement for Command Prompt.

Command Prompt had been modified, to make the window
a bit more re-sizable. The new Terminal window, is
sorta along the same lines as the Visual-Studio-like
source editor. (Now, where did I leave that, it's
around here somewhere. Etc.)

The biggest improvement in Notepad, is "now it actually
works". You can do 100,000 Find-Replace and it finishes
in a couple seconds. Older versions of Notepad, it
seemed to "reformat the window after each Find-Replace,
instead of waiting until all the Find-Replace were
completed", which is dumb as dirt. And they finally
fixed that. But they also went overboard, by putting
in the text file declaration bytes at the beginning
of text files. Which may not be compatible with other
tools later (legacy tools for the vanilla ASCII character
set).

I guess using a computer must perpetually be like
herding turtles. When your back is turned, the turtles
wander off at warp speed.

Paul