Return to Answer

vd (visidata), though written in python3, when input is coming from stdin doesn't seem to honour $PYTHONIOENCODING, and in the C or C.UTF-8 locales doesn't seem to be doing that surrogate escaping, but calling it in a locale that uses the latin1 charset seems to work so you can do:

Though I find it sometimes fails randomly for non-regular files such as those pipes. Using a format with one json perl line (jsonl) works better:

vd -f jsonl =(lsfd -J | binary jq -c '.lsfd[]') 

Or use the =(...) form of process substitution in zsh that uses a temp file instead of pipes:

vd (visidata), though written in python3, when input is coming from stdin doesn't seem to honour $PYTHONIOENCODING, and in the C or C.UTF-8 locales doesn't seem to be doing that surrogate escaping (see this issue), but calling it with --encoding=latin1 with version 2.5 or newer (where that issue was fixed) or in a locale that uses the latin1 charset seems to work so you can do:

However, I find it sometimes fails randomly for non-regular files such as those pipes (see that other issue). Using a format with one json perl line (jsonl) works better:

vd -f jsonl <(lsfd -J | binary jq -c '.lsfd[]') 

Or use the =(...) form of process substitution in zsh (or (...|psub -f) in fish, same as (...|psub) in current versions) that uses a temp file instead of a pipe:

Though I find it sometimes fails randomly for non-regular files such as those pipes. Using a format with one json perl line (jsonl) works better:

vd -f jsonl =(lsfd -J | binary jq -c '.lsfd[]') 

Or use the =(...) form of process substitution in zsh that uses a temp file instead of pipes:

vd -f json =(lsfd -J | binary jq .lsfd) 

vd (visidata), though written in python3 doesn't seem to honour $PYTHONIOENCODING, and in the C or C.UTF-8 locales doesn't seem to be doing that surrogate escaping, but calling it in a locale that uses the latin1 charset seems to work as in:

For a visual lsfd that doesn't crash if there are command or file names that are not UTF-8 encoded text.

vd (visidata), though written in python3, when input is coming from stdin doesn't seem to honour $PYTHONIOENCODING, and in the C or C.UTF-8 locales doesn't seem to be doing that surrogate escaping, but calling it in a locale that uses the latin1 charset seems to work so you can do:

For a visual lsfd that doesn't crash if there are command or file names in the output of lsfd -J that are not UTF-8 encoded text.

When passing the JSON file as the path of a file as argument, then it seems to decode the input as per the --encoding and --encoding-errors options which by default are utf-8 and surrogateescape respectively, and honour the locale's charset for output.

So, in a shell with process substitution support such as ksh, zsh, bash (or rc, es, akanga with a different syntax), you can just do:

vd -f json <(lsfd -J | binary jq .lsfd)