Windows text files can start with a byte order mark of U+FEFF and then
be encoded in UTF-8. These are skipped as being binary files.
opped a requirement for them? That doesn't
necessarily mean things must be deprecated.
/Simon
signature.asc
Description: PGP signature
m | grep -E "[0-9a-f]+" -o | xxd -r
-p | base32 | grep -E "[0-9A-Z]+" -o
LCBSPBBX6BY6
VZX6P6TZMMRETTCSPXZU7GJTAPPZCPKF2UJEYDA
jas@latte:~$ LANG=C
jas@latte:~$ echo -n ":egov" | sha256sum | grep -E "[0-9a-f]+" -o | xxd -r
-p | base32 | grep -E "[0-9A-Z]+" -o
LCBSPBBX6BY6WVZX6P6TZMMRETTCSPXZU7GJTAPPZCPKF2UJEYDA
jas@latte:~$
/Simon
signature.asc
Description: PGP signature
), there
is no egrep and fgrep any more, and dealing with non-existing tools
(discover the error, then use egrep -E or add a personal alias for
interactive use) is easier than dealing with annoying warnings that
cannot be disabled.
/Simon
signature.asc
Description: PGP signature
SIX?
Personally, I'd rather have tools exit with an error code on invalid
uses rather than issuing warning messages.
/Simon
signature.asc
Description: PGP signature
which feels a bit unsatisfying...
How about saying that the envvar, together with all remaining traces of
[ef]grep references will be removed in 2025?
The point with the excercise was (at least to me) to remove complexity,
but it seems we will have to wait some more until that can happen.
