How to remove ^M character in Vim?

The ^M character in Vim is a visual representation of a carriage return (CR, ASCII 0x0D) from Windows or DOS-style line endings, appearing when a file created in that environment is opened in a Unix-like system where only a line feed (LF) character terminates a line. The core solution involves using Vim's substitution command to replace the carriage return characters. The most direct and reliable method is to execute the command `:%s/^M//g` within Vim's command-line mode. It is critical to note that the `^M` in this command is not typed as two separate characters; it is entered by pressing `Ctrl-V` followed by `Ctrl-M`, which produces the single control character representation. This command globally searches the entire file (`%`) and substitutes every instance of the carriage return with nothing, effectively removing it and converting the line endings to the Unix standard.

The mechanism of this operation relies on Vim's pattern matching and the nature of the file's internal representation. When Vim opens a file with CRLF line endings, it interprets the LF as the line terminator for editing purposes but may display the preceding CR as `^M`. The substitution command works on the raw buffer content, matching the actual CR character. An alternative, more explicit pattern is `:%s/\r//g`, where `\r` in a Vim substitution pattern specifically matches a carriage return character. This can be more intuitive and less error-prone than the key combination. For tasks involving multiple files, one can use Vim's argument list with `:argdo %s/\r//g | update` to process all loaded files and save them. It is also prudent to set the `'fileformat'` option to `'unix'` after the substitution with `:set ff=unix`, which instructs Vim to write the file using LF line endings, preventing the issue from recurring on save.

The implications of this correction extend beyond mere visual cleanup. Removing extraneous carriage returns is often a necessary preprocessing step for shell scripts, configuration files, or source code intended to execute on Unix, Linux, or macOS systems, as the presence of a CR can cause syntax errors, failed command execution, or other unpredictable behavior. For instance, a shebang line like `#!/bin/bash^M` will be interpreted incorrectly by the kernel. While Vim can handle various file formats, consistent line endings are crucial for interoperability. If the goal is to convert line endings rather than delete all CR characters—for instance, if CRs appear in the middle of a line—a more nuanced approach like `:%s/\r$//` would target only carriage returns at line endings, though the standalone `^M` character typically appears precisely there due to the file format. Understanding this distinction is key for robust text file management across operating systems.