How can I make all line endings (EOLs) in all files in Visual Studio Code, Unix-like?

WindowsBashVisual Studio-CodeEditorLine Endings

Windows Problem Overview


I use Windows 10 Home and I usually use Visual Studio Code (VS Code) to edit Linux Bash scripts as well as PHP and JavaScript.

I don't develop anything dedicated for Windows and I wouldn't mind that the default EOLs for all files I edit whatsoever would be Unix like (nix).

How could I ensure that all EOLs, in all files whatsoever (from whatever file extension), are nix, in Visual Studio Code?


I ask this question after I've written a few Bash scripts in Windows with Visual Studio Code, uploaded them to GitHub as part of a project, and a senior programmer that reviewed the project told me I have Windows EOLs there and also a BOM problem that I could solve if I'll change the EOLs there to be nix (or that's what I understood, at least).


Because all my development is Linux-oriented, I would prefer that by default, any file I edit would have nix EOLs, even if it's Windows unique.

Windows Solutions


Solution 1 - Windows

The accepted answer explains how to do this for all files (use files.eol in settings), but if you ever need to override that setting there's an indicator at the bottom right that you can click on and change for this one file. Took me a while to notice that this was clickable.

See CRLF in the message bar at the bottom right

Solution 2 - Windows

I searched for a simple solution for days and didn't have any success after I found some Git commands that changed all files from CRLF to LF.

As pointed out by Mats, make sure to commit changes before executing the following commands.

In the root folder type the following.

git config core.autocrlf false

git rm --cached -r .         # Don’t forget the dot at the end

git reset --hard

Solution 3 - Windows

In your project preferences, add/edit the following configuration option:

"files.eol": "\n"

This was added as of commit 639a3cb, so you would obviously need to be using a version after that commit.

Note: Even if you have a single CRLF in the file, the above setting will be ignored and the whole file will be converted to CRLF. You first need to convert all CRLF into LF before you can open it in Visual Studio Code.

See also: https://github.com/Microsoft/vscode/issues/2957

Solution 4 - Windows

You can find the option in Visual Studio Code settings. It's under "Text Editor"→"Files"→"Eol". Here you can select whether you want \n or \r\n or auto.

Enter image description here

Solution 5 - Windows

To convert the line ending for existing files

We can use dos2unix in WSL or in your Shell terminal.

Install the tool:

sudo apt install dos2unix

Convert line endings in the current directory:

find -type f -print0 | xargs -0 dos2unix

If there are some folders that you'd want to exclude from the conversion, use:

find -type f \
     -not -path "./<dir_to_exclude>/*" \
     -not -path "./<other_dir_to_exclude>/*" \
     -print0 | xargs -0 dos2unix

Solution 6 - Windows

Both existing answers are helpful but not what I needed. I wanted to bulk convert all the newline characters in my workspace from CRLF to LF.

I made a simple extension to do it

https://marketplace.visualstudio.com/items?itemName=vs-publisher-1448185.keyoti-changeallendoflinesequence

In fact, here is the extension code for reference

'use strict';

import * as vscode from 'vscode';
import { posix } from 'path';


export function activate(context: vscode.ExtensionContext) {

	// Runs 'Change All End Of Line Sequence' on all files of specified type.
	vscode.commands.registerCommand('keyoti/changealleol', async function () {

		async function convertLineEndingsInFilesInFolder(folder: vscode.Uri, fileTypeArray: Array<string>, newEnding: string): Promise<{ count: number }> {
			let count = 0;
			for (const [name, type] of await vscode.workspace.fs.readDirectory(folder)) {

				if (type === vscode.FileType.File && fileTypeArray.filter( (el)=>{return name.endsWith(el);} ).length>0){ 
					const filePath = posix.join(folder.path, name);
					
					var doc = await vscode.workspace.openTextDocument(filePath);
						
					await vscode.window.showTextDocument(doc);
					if(vscode.window.activeTextEditor!==null){
						await vscode.window.activeTextEditor!.edit(builder => { 
							if(newEnding==="LF"){
								builder.setEndOfLine(vscode.EndOfLine.LF);
							} else {
								builder.setEndOfLine(vscode.EndOfLine.CRLF);
							}
							count ++; 
						});
						
					} else {
						vscode.window.showInformationMessage(doc.uri.toString());
					}
				}

				if (type === vscode.FileType.Directory && !name.startsWith(".")){
					count += (await convertLineEndingsInFilesInFolder(vscode.Uri.file(posix.join(folder.path, name)), fileTypeArray, newEnding)).count;
				}
			}
			return { count };
		}

		let options: vscode.InputBoxOptions = {prompt: "File types to convert", placeHolder: ".cs, .txt", ignoreFocusOut: true};
		let fileTypes = await vscode.window.showInputBox(options);
		fileTypes = fileTypes!.replace(' ', '');
		let fileTypeArray: Array<string> = [];

		let newEnding = await vscode.window.showQuickPick(["LF", "CRLF"]);

		if(fileTypes!==null && newEnding!=null){
			fileTypeArray = fileTypes!.split(',');
		
			if(vscode.workspace.workspaceFolders!==null && vscode.workspace.workspaceFolders!.length>0){
				const folderUri = vscode.workspace.workspaceFolders![0].uri;
				const info = await convertLineEndingsInFilesInFolder(folderUri, fileTypeArray, newEnding);
				vscode.window.showInformationMessage(info.count+" files converted");
			
			}
		}
		
	});

}

Solution 7 - Windows

For other people asking you can use the "Files.eol" setting is Visual Studio Code to change the line ending for every file.

"Files.eol": "\n"   // Unix
"Files.eol": "\r\n" // Windows

Solution 8 - Windows

I've just faced the same issue on my Windows machine. Every time I opened a file it would set the EOL to CRLF (even though I explicitly set up a configuration for lf as people suggested). It appeared, that the problem is that I cloned my repository with the wrong Git configuration. It was CRLF by default. Anyway, here's what I did and it worked perfectly. No more CRLF in my workspace.

  1. Set up your Git configuration to lf with the command git config --global core.autocrlf false
  2. Now clone your project again: git clone ...
  3. Set up your Visual Studio Code instance, menu FilePreferencesSettingsFiles: Eol to "\n".
  4. Open the project, and everything should be as expected

Solution 9 - Windows

Uninstall typescript

run

npm install -g typescript
git config --global core.autocrlf false

check

git config --global core.autocrlf 

if it shows false. try to clone and re-run the project

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
Questionuser9303970View Question on Stackoverflow
Solution 1 - WindowsIan McGowanView Answer on Stackoverflow
Solution 2 - WindowshaidarView Answer on Stackoverflow
Solution 3 - WindowsMikeView Answer on Stackoverflow
Solution 4 - WindowsJoaquin CayrusView Answer on Stackoverflow
Solution 5 - WindowsJesusIniestaView Answer on Stackoverflow
Solution 6 - WindowsJim W says reinstate MonicaView Answer on Stackoverflow
Solution 7 - WindowsAndrew VelezView Answer on Stackoverflow
Solution 8 - WindowsViktor ChernodubView Answer on Stackoverflow
Solution 9 - Windowspiash tanjinView Answer on Stackoverflow