Tabular data converter sidekick

Two everyday authoring chores, from the keyboard:

1. Convert a selected table between CSV, Markdown and HTML — all six directions.
2. Round-trip tables through Excel via the clipboard.
3. Extract Markdown headings from a selection or a whole document.
4. Save regex find/replace recipes and recall them straight into VS Code's Find/Replace widget.

Commands & default keybindings

Every command sits under the PK Tools category, so typing pk in the Command Palette (Ctrl+Shift+P) lists all ten at once.

The editor right-click menu carries a PK Tools submenu with six everyday entries — Convert Table…, Paste Table as…, Copy Selection as Excel Cells and Regex Find/Replace Snippet…, plus Extract Markdown Headings and Right-align Numeric Columns in Markdown Table. The two "…" pickers cover every target format, so the three explicit Convert Table to Markdown/HTML/CSV commands and Paste Excel Cells as Markdown Table are left off the menu to keep it short; they are still in the Command Palette and still bindable. The submenu is always there while an editor has focus, whether or not you have a selection.

VS Code keybindings are keyboard-only; a mouse chord such as Alt+right-click cannot be bound to a command, which is why the submenu hangs off the plain right-click menu.

All commands are ordinary VS Code commands — remap them in File → Preferences → Keyboard Shortcuts, or in keybindings.json:

{ "key": "ctrl+alt+m", "command": "pkTools.convertTableToMarkdown", "when": "editorTextFocus" }

Markdown heading extraction

Run Extract Markdown Headings with text selected to extract headings only from that selection. With an empty selection, the command scans the whole document. The headings open in a new untitled editor beside the source with the language mode set to Markdown; the original document is not changed.

ATX headings (# Heading through ###### Heading) and Setext headings (text followed by === or ---) are preserved in document order. Heading-like text inside fenced or indented code blocks is ignored.

Table conversion

Select a table and run a convert command. The source format is detected automatically, which is why three "convert to" commands cover all six directions.

The result opens in a new editor beside the original with the matching language mode. Your original text is never modified.

With nothing selected, the whole document is converted.

a,b,c              | a | b | c |            <table>
1,2,3       →      | --- | --- | --- |  →     <thead>
                   | 1 | 2 | 3 |                <tr>
                                                  <th>a</th>

Automatic column alignment

When the target is Markdown, each column's alignment is inferred from its values:

| product    | units |     price |   launched |    at | active |
| :--------- | ----: | --------: | ---------: | ----: | :----: |
| Widget     |  1200 |    $35.50 | 2026-07-21 | 09:30 |  TRUE  |
| Gadget Pro |    85 | $1,240.00 | 2026-08-01 | 14:05 | FALSE  |

A column takes a type only when every value agrees — one about 80 among the numbers makes the whole column text. Blanks and null-ish markers (N/A, null, -, NaN) are skipped, so a stray gap doesn't demote a numeric column.

The header is ignored when inferring, since it's a label rather than data — a quantity column of numbers still aligns right.

Alignment the source already specifies — an HTML text-align, a Markdown ---: — is explicit intent and always wins over inference. Turn the whole feature off with "pkTools.alignColumnsByType": false.

To update an existing Markdown table in place, place the cursor anywhere inside the table and run Right-align Numeric Columns in Markdown Table from the Command Palette or the editor's PK Tools submenu. The command automatically selects the table around the cursor; an explicit selection still takes precedence. If that selection contains multiple tables, every table is processed independently while headings, paragraphs, and whitespace between them are preserved. It changes only numeric separator cells to ---: and preserves every other line. In addition to plain numbers, it recognizes report-style values such as 777 (77.7%), 84.7K THB, **2.57B THB**, 41 sqm, 14.2×, +1.59, −0.27, and 1.72B THB (latent). Numerical ranges such as 1–30, 1-30, 1 to 30, $10–$20, and 1.5M–2.0M THB are numeric too. Mixed narrative values remain unchanged.

What it handles

• CSV — RFC 4180: " quoting, "" escapes, delimiters and newlines inside quoted fields, CRLF or LF. The delimiter is sniffed (, ; tab |) unless you pin it with pkTools.csvDelimiter.
• Markdown — optional outer pipes, column alignment (:---, :---:, ---:) is read and preserved, \| escapes survive round trips, and cell newlines become <br>.
• HTML — <thead>/<tbody> or a bare <tr> list, entity decoding, inline tags stripped from cells, text-align mapped to Markdown alignment. If there is no <th>, the first row becomes the header.
• Ragged rows are padded to the header width rather than producing a broken table.

Limitation: the HTML reader targets well-formed table fragments, not arbitrary HTML. Nested tables and colspan/rowspan are not supported — this is the trade-off for shipping with zero dependencies.

Excel round trip

Excel → Markdown

Copy a range of cells in Excel, then press Ctrl+Alt+V in your document. The cells arrive as a formatted Markdown table at the cursor (replacing the selection, if any).

Excel puts tab-separated text on the clipboard, so cells containing commas stay whole — Oslo, NO lands in one column, not two. Cells with line breaks or quotes come through correctly too. The clipboard may equally hold HTML (copied from a web page) or an existing Markdown table; the source is detected either way.

Excel → CSV (or HTML)

Paste Table as… does the same at the cursor, but asks for the target format first — Markdown, CSV, or HTML. Copy a range in Excel, run it, pick CSV, and the cells land as proper CSV: the delimiter is the one from pkTools.csvDelimiter, and quoting follows the column rule below.

Ctrl+Alt+V stays on the Markdown-only paste, so the fast path is unchanged.

Automatic quoting, by column

CSV output quotes a value whenever it contains the delimiter, a ", or a line break — and then quotes every other value in that column too, so a column reads consistently instead of alternating between quoted and bare rows. Columns that never need quotes stay bare, and the header row is quoted only if the header text itself needs it.

id,name,note
1,"Smith, John",ok
2,"Lee","has
comma, here"

id is untouched; name and note are quoted throughout. Values inside quotes are escaped RFC 4180-style (" becomes ""), so the result parses straight back to the original cells.

The TSV written for Excel's clipboard is the exception — it keeps the minimum quoting, since Excel reads clipboard quotes inconsistently and a tab inside a cell is rare.

Markdown → Excel

Copy Selection as Excel Cells puts tab-separated, CRLF-terminated text on the clipboard, ready to paste straight into a worksheet — Excel drops it into proper cells rather than one column of text.

It takes its source from:

• your selection, if you have one; or
• the clipboard, if nothing is selected — so a Markdown table you just copied from somewhere else can be made Excel-pasteable without dropping it into an editor first.

CSV, Markdown and HTML tables are all accepted as input.

When the source is a Markdown table, its inline formatting is markup rather than data, so it is dropped: **1,250** arrives as the number 1,250, `42` as 42, and [Docs](https://…) as Docs. Emphasis, strikethrough, code spans, links, images and styling tags such as <b> are all removed; a backslash-escaped \* stays literal, and snake_case_id keeps its underscores.

Cell whitespace is tidied along with it — a run of spaces or tabs collapses to one, a non-breaking space becomes an ordinary one, and the padding around a <br> line break goes — so the alignment spaces an author used to line the Markdown source up never reach the worksheet. The same applies to Convert Table to CSV/HTML and Paste Table as… CSV/HTML — Markdown output keeps its formatting, and formatting characters in a CSV or HTML source are data and are left alone.

Excel always separates columns with tabs, so clipboard text with no tab at all is read as a single column. That is what keeps a lone column of Smith, John values intact. Text with a consistent , or ; on every line is still recognised as real CSV.

Regex find/replace snippets

Press Ctrl+Alt+R, pick a recipe, and the native Find/Replace widget opens with the pattern, the replacement, and the regex toggle already set. You review the matches and press Replace All — nothing is changed behind your back.

Typing in the Quick Pick matches the pattern as well as the name, so searching cita or \[.*\] both find the citation stripper.

Built-in snippets

Turn these off with "pkTools.includeBuiltInSnippets": false.

Adding your own

"pkTools.regexSnippets": [
  {
    "name": "Strip footnote markers",
    "find": "\\[\\^\\d+\\]",
    "replace": "",
    "description": "Remove [^1]-style footnote references"
  },
  {
    "name": "Thai digits → Arabic",
    "find": "[๐-๙]",
    "replace": "",
    "isRegex": true
  }
]

Settings are JSON, so backslashes are doubled: the regex \[.*\] is written "\\[.*\\]".

Reusing a built-in's name overrides that built-in in place, so you can tweak one without losing the rest. A snippet whose pattern does not compile is skipped with a warning rather than breaking the list.

Set replace explicitly — even to "". VS Code only reveals the replace box when a replacement string is supplied, so an omitted replace opens find-only.

Settings

Contributing

Building, testing and publishing this extension are covered in DEV.md.

License

MIT