![]() VS2019 itself creates files with mixed line endings, and then complains about it. It's kinda annoying and couldn't find anything useful on google, can anyone help me out? Visual Studio for Mac.NET. Many text editors can fix this using Convert Line Endings menu commands. ![]() This might lead to incorrect line numbers in stacktraces and compiler errors. Some are Mac OS X (UNIX) and some are Windows. Error: There are inconsistent line endings in the script. LS: Line separator, Unicode character 2028. The following characters are interpreted as line breaks in Visual Studio: CR LF: Carriage return + line feed, Unicode characters 000D + 000A. ![]() For example, this can happen when importing 3rd-party code from a package in the Unity Asset Store, when working on a project using both Windows and Mac machines, or when using multiple text editors or IDEs to write scripts (such as Microsoft Visual Studio and Unity MonoDevelop). It sometimes happens that you run into 'inconsistent line ending' warnings when using the Unity Editor. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |