More helpful saving and format options about visidata HOT 5 OPEN

To answer your first question, I went through and looked in the source for def open_*() and def save_*()
Here's a list of every extension/filetype that visidata can read+write:

arrow         gsheets       npy           tsv           xd
arrows        html          org           txt           xls
csv           jrnl          parquet       usv           xlsx
dta           jsonl         png           vdj           xml
fixed         jsonla        rec           vds           zip
geojson       lsv           sqlite        vdx

And here's what it can read, but not write:

airtable      forg          mh            pdf           toml
babyl         frictionless  mmdf          puz           ttf
bytes         gdrive        mnu           pyprof        vcf
conll         git           npz           reddit        vd
conllu        h5            ods           sas7bdat      xlsb
eml           jsonobj       orgdir        scrape        xpt
f5log         maildir       pandas        shp           yml
fdir          mbox          pbf           spss          zulip
fec           mbtiles       pcap          tar

And there seem to be a few it can write but not read: dot svg. And there are several extensions that are not exactly full-fledged file types, they are types of tables in the tabulate library, for table files (see loaders/texttable.py. The list of these includes jira md table (and more) that it can write, but not read.

Where is a good place you'd like to see this information? It could go in a table like https://visidata.org/docs/formats/, perhaps in one of the guides? Accessible by a command like open-format-guide?

from visidata.

It's not clear if multiple extensions work (i.e., format+compression).

This does not work currently, but it's on my wishlist too. I'd be interested in a PR that addressed this.

from visidata.

the resulting file BestofRedditorUpdates_submissions.vds.zst is smaller, but cannot be reopened: "Unsupported operation: Underlying stream is not seakable."

Can the file be decompressed manually and then opened as .vds? If so, then it's likely a bug in the vds loader (otherwise it's a bug in the vds saver). This is a bug either way though.

Also I would support vdz as an alias for vds+zstd when that's possible.

from visidata.

I'm not sure what the best way to do this is, but some thoughts:

• Give the user a choice of formats to save in. I don't know how to prompt this, as tab autocompletion works on the filename presently, but perhaps some other shortcut?
• If the user specifies a filename with an extension for which there is not a save format, warn them. ("are you sure?" with explanation in sidebar?)

from visidata.

@saulpw I loaded the vds file, saved it as BestofRedditorUpdates_submissions.vds.zstd, which is a smaller file size, but am unable to decompress manually.

❯ zstd --decompress BestofRedditorUpdates_submissions.vds.zstd
zstd: BestofRedditorUpdates_submissions.vds already exists; overwrite (y/n) ? y
zstd: BestofRedditorUpdates_submissions.vds.zstd: unsupported format

from visidata.