Editing Cells

← Contents

TableSkim opens files for viewing, and nothing you do changes a file unless you turn on edit mode. In edit mode you can change the values of cells and save the file again.

FormatEditing
CSV, TSV, VCF and other text files (compressed too)Yes
Excel (.xlsx, .xlsm)Yes
Parquet, JSON, DuckDB, SQLite, SQL resultsNo

Only cell values change: rows and columns cannot be added or removed.

Edit mode

Edit mode applies to every sheet of the file. It stays on when the file is saved or reloaded, and it is off when another file is opened. Turning it off with unsaved changes asks whether to save them first.

Changing cells

In the GUI:

A cell of a frozen column is edited in a small dialog.

In the terminal UI:

Outside edit mode these keys keep their usual meaning (for example Enter shows the cell in the sidebar).

Edited cells are shown in green until the file is saved, and the title (GUI) or status bar (terminal UI) starts with * while there are unsaved changes. Undo and Redo work for each sheet separately.

What a cell becomes

Some cells cannot be edited: Excel formulas, error values and times shown as text (hh:mm:ss, [h]:mm:ss), cells covered by a merged cell (except its top-left cell), the header row, and rows that have not been read yet.

Sorting and filtering

An edited row stays where it is: the sort and filter are applied again only when you change them, as in a spreadsheet. Searches, column statistics and histograms start over with the new values.

Saving

Saving keeps everything you did not change:

The new file is written next to the original and replaces it only when it is complete, so a failed save leaves the file as it was. The file keeps its permissions, and a symbolic link keeps pointing to it. After saving, the file is opened again (the position, sort and filter stay), and Undo starts over.

If another program has changed the file since TableSkim opened it, saving fails; use Save As, or reload the file (which drops your changes).

A bgzip file is written in bgzip blocks again, but an index made for it (.tbi, .csi) no longer matches and must be made again.

Unsaved changes

TableSkim asks before unsaved changes would be lost: when the window is closed, when quitting, when reloading the file (Revert), and when changing the header, ## or encoding option, which read the file again.

While there are unsaved changes, Auto Revert does not reload the file. If the file changes on disk meanwhile, the title or status bar says (changed on disk).

Export View writes the sheet with the unsaved changes; Convert to Parquet / DuckDB reads the file and so converts it as it was last saved. See Exporting and Converting.