encrypted file not recognized as binary

[dougg0k]

What steps will reproduce the bug?

1. Try to use bat in a gpg encrypted file.

tar -cvzf uncrypted_folder.tar.gz uncrypted_folder
gpg --symmetric --batch --yes --passphrase-file keyfile.key --cipher-algo AES256 --output encrypted_filename.tar.enc unencrypted_folder.tar.gz

What happens?
If I try to use the tool to read a gpg encrypted file, it has apper glyphs issues and does not recognize as binary as it should. It didnt happen in all enc files, but it did in most.

I tested in 3 different terms, all same issue.

What did you expect to happen instead?
Show nothing or just be recognized as binary file.

---

bat 0.26.1 (979ba22)

No fonts contain glyphs for these codepoints: \u{7b4}.
Placeholder glyphs are being displayed instead.
You may wish to install additional fonts, or adjust
your configuration so that it can find them.
Set warn_about_missing_glyphs=false to suppress this
message. 

[keith-hall]

bat uses the content_inspector crate to determine if the input is considered binary or not, and it passes it the first line of the input. content_inspector itself only looks at the first 1024 bytes to see if it contains a NULL byte. So I'm guessing your encrypted content doesn't meet this criteria...

[dougg0k]

Just asked chatgpt about this and file/file, here is the recommendation

Practical recommendations

If you want file-equivalent behavior:
→ use libmagic bindings (magic crate).

If you only need MIME / extension guessing:
→ use infer or tree_magic_mini.

If you are building tooling (e.g., Rust-based CLI replacing shell tools):
→ combine:

infer for quick classification
goblin / object for binaries
text/binary detection via content_inspector

But there is currently no pure-Rust, general, rule-database-driven replacement for file(1).