chars

I wrote a CLI program to determine and detect the end-of-line format, tabs, bom, and nul characters. It can be installed via Homebrew or you can download standalone binaries for all platforms: https://github.com/jftuga/chars

I wrote a standalone CLI tool (written in Go) to determine and detect the end-of-line format, tabs, bom, and nul characters: https://github.com/jftuga/chars

I wrote a command line program to determine/detect the end-of-line format, tabs, bom, and nul characters https://github.com/jftuga/chars Stand-alone binaries are provided for all major platforms.

These are all CLI... https://github.com/jftuga/less-Windows - [not really mine, but I just help maintain the port] - GNU less compiled for Windows 10 & 11. Stand-alone version with no dependencies. https://github.com/jftuga/gofwd - A cross-platform TCP port forwarder with Duo 2FA and Geo-IP integration https://github.com/jftuga/spotprice - Quickly get AWS spot instance pricing - a bit easier to use than the aws cli; is also faster and has more features https://github.com/jftuga/tcpscan - A standalone, fast, simple, multi-threaded cross-platform IPv4 TCP port scanner https://github.com/jftuga/ipinfo - Return IP address info including geographic location and distance when given IP address, email address, host name or URL https://github.com/jftuga/photo_id_resizer - Resize photo ID images using face recognition technology https://github.com/

I added a new command line switch, -F * when used with -f, only display a list of failed files, one per line https://github.com/jftuga/chars/releases/tag/v2.3.0

Thanks for the issue, I've subscribed to it. https://github.com/jftuga/chars/issues/2 According to the page, several machines and operating systems used CR as EOL. While the systems are all obsolete, files from that era that use CR as EOL could persist and be transferred to modern systems. Clearly those are weird on modern systems, so they should be warned about in a linting situation, which I would like to use your project 'chars' in. Having different EOL chars within the same file is definitely a thing, usually by mistake. I had to fix a bug about this recently: https://github.com/EionRobb/purple-discord/pull/416

I wrote a cross platform, stand alone cli program to do this. It determines the end-of-line format, tabs, bom, and nul characters: https://github.com/jftuga/chars

See my other comment in this thread about my project: https://github.com/jftuga/chars

I have written a cross platform, stand alone CLI program to inspect a file for BOM8 and BOM16. It also detects if a file uses CRLF or LF. Tab and nul characters are also evaluated. Please see the Examples in my repo: https://github.com/jftuga/chars

I just finished off a program to show which files use CRLF and which use LF. It also shows results for TAB, NUL, BOM-8 and BOM-16: https://github.com/jftuga/chars You can use the -f switch to help with pipelines and -j for JSON output.