You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to feed in binary data through the terminal and am expecting binary data in return. Apparently setting any input file, whether /dev/stdin or the source file itself, makes something along the way expect UTF-8 text. That something then spams [Invalid UTF-8] for each wrong byte. This cannot be the terminal I'm running, since it occurs when redirecting the output to a file, too. I admit it's a strange use case, but so is Brainfuck in the first place.
Minimal reproducible example under Debian Bullseye:
I'm trying to feed in binary data through the terminal and am expecting binary data in return. Apparently setting any input file, whether /dev/stdin or the source file itself, makes something along the way expect UTF-8 text. That something then spams
[Invalid UTF-8]
for each wrong byte. This cannot be the terminal I'm running, since it occurs when redirecting the output to a file, too. I admit it's a strange use case, but so is Brainfuck in the first place.Minimal reproducible example under Debian Bullseye:
test.bf:
In terminal:
This also happens when piping in input like so:
beef test.bf < test.bf
The text was updated successfully, but these errors were encountered: