Hi, uutils mainteners
to reproduce that incorrect error messages behavior you need do simply
relunsec@relunsec:~/software/coreutils/target/debug$ ./base32 a/
base32: a/: No such file or directory
the same with base64
relunsec@relunsec:~/software/coreutils/target/debug$ ./base64 a/
base64: a/: No such file or directory
as i see the gnu version displays the correct error message
relunsec@relunsec:~/software/coreutils/target/debug$ gnubase32 a/
gnubase32: a/: Not a directory
relunsec@relunsec:~/software/coreutils/target/debug$ gnubase64 a/
gnubase64: a/: Not a directory
relunsec@relunsec:~/software/coreutils/target/debug$
a in that case is a regular file appending, / to it cause a non such file or directory instead of the expected not a directory error message
Hi, uutils mainteners
to reproduce that incorrect error messages behavior you need do simply
the same with base64
as i see the gnu version displays the correct error message
a in that case is a regular file appending, / to it cause a non such file or directory instead of the expected not a directory error message