Many other things can lead to this such as when Unity changes code for you in your scripts (API updater). I don't think Visual Studio will convert the line endings for you when pasting from a file that uses different line endings. You can also choose a specific line ending style in most editors.)Ĭlick to expand.Copying and pasting code in that uses different line endings could definitely do it. (Generally, text editors will detect the new line style being used and won't mix new line code types regardless of the operating system in use. That's what the 'inconsistent line endings' warning is telling you. If you open a text file on a Unix-based machine (Mac), it will encode new lines with one character, then you modify that file on a Windows-based machine, it may use Windows-style new line codes when you insert new lines. (Some text editors allow you to see the line ending code if you enabled it.) Developers of the different operating systems made different decisions as to which character codes to use to end a line in a text file way back in the early days of the operating systems. They are hidden, but are embedded in the text file (.cs file). You never see the line endings in your code. They appear at the end of every single line in a text file. Line endings refer to the invisible character code used to signify a new line. Line endings have nothing to do with how you manually end your lines.

You can also choose a specific line ending style in most editors.)

Click to expand.Line endings have nothing to do with how you manually end your lines.

Notepad++ mac ucsd