eol

List all available products

$ eol

$ eol [product1 product2 ...]

$ eol [product] [[-w|--web]]

$ eol [product1 product2 ...] --[html|json|md|markdown|pretty|rst|csv|tsv|yaml]

$ eol [product1 product2 ...] --[markdown] > [eol_report.md]

$ eol [[-h|--help]]

eol [OPTIONS] [FILE]...

-u
    Convert to Unix LF format

-d
    Convert to DOS CRLF format

-m
    Convert to Mac CR format

-i
    Show info about file EOL types

--in-place
    Edit files in place

-h
    Display help

--version
    Show version info

The eol command is not a standard Linux utility included in core distributions like GNU coreutils or busybox. It may refer to custom scripts, aliases, or third-party tools for handling end-of-line (EOL) characters, such as converting between Unix LF (\n), Windows CRLF (\r\n), or Mac CR (\r) formats. Common use cases involve text file conversion in cross-platform environments.

Without a standard implementation, 'eol' is often a wrapper or function defined in user environments, dotfiles, or packages like dos2unix alternatives. Searching package managers (apt, yum) yields no matches for a binary named 'eol'. Developers might encounter it in proprietary software, build scripts, or Git hooks for line-ending normalization.

If invoked as-is, typical shells report 'command not found'. For EOL tasks, standard tools like dos2unix, unix2dos, sed, or perl are recommended instead.

Not standard; may not exist on your system. Use dos2unix(1) or sed as reliable alternatives. Custom implementations vary and may lack portability.

Use dos2unix file.txt for LF-to-CRLF or sed -i 's/\r$//' to strip CR.

Git uses core.autocrlf and eol attributes in .gitattributes for repo-wide EOL handling.

No official history as a standard command. EOL conversion tools trace to 1980s Unix with uuto precursors; modern utils like dos2unix from 1990s. Custom 'eol' scripts proliferate in devops since 2000s for Git normalization.

dos2unix(1), unix2dos(1), sed(1), recode(1), col(1)