Hey @midichef!

I'm trying to confirm this worked with find visidata -print0 | vd --row-delimiter='', but it does not to be seperating the output into rows:

Is there something I am testing incorrectly?

Right now the option will only apply when the filetype is tsv. So the command would need to be find visidata -print0 | vd -f tsv --row-delimiter=''

I added some warnings when the field/row delimiter is NUL, because it may surprise people. One situation I'm thinking of is: someone has run vd file.tsv and is exploring the options sheet after hitting O. They hit e to edit the blank cell for the global option for delimiter. In that cell appears the · character (disp_unprintable, for '\t'). They erase it and hit Enter. The blank cell looks the same as before they started editing it, so they don't think much of it. But they have unwittingly overwritten the default value of vd.options.delimiter with the empty string '', so the actual delimiter will be '\0'. Then they save their TSV file, and it's full of '\0'. And life is less great. A warning can help them realize what happened.

The issue is more complicated than I realized though. How should we handle comments when the delimiter is NUL?

i.e. TsvSheet.options.regex_skip = '^#.*' will currently skip over lines that look like comments. But it should definitely not do that when handling the output of find -print0.

My intuition is, regex_skip should not be used when the row delimiter is NUL, as we're not in classic TSV format any more.

My intuition is, regex_skip should not be used when the row delimiter is NUL, as we're not in classic TSV format any more.

I would say, let's add that to an issue as a follow-up task, but get this piece merged in for now. No need to block the PR.