Treat ${0} as the final snippet tab stop #30

Merged

marijn merged 1 commit from ondrejmirtes/autocomplete:snippet-final-stop into main

2026-06-02 21:14:50 +02:00

ondrejmirtes commented

2026-05-22 09:17:23 +02:00

Contributor

Snippet field order is by number, but ${0} should be the final/exit stop --
the position the cursor lands on after tabbing through the other fields --
matching the convention used by TextMate, LSP, VS Code, and others. It was
treated as plain field 0 and sorted first, so a snippet like foo(${1:bar})${0}
selected the empty ${0} instead of bar.

This orders ${0} after every other field (numbered and named), so the first
real placeholder is selected and ${0} becomes the exit. Documented in the
snippet docstring; test added.

Snippet field order is by number, but `${0}` should be the final/exit stop -- the position the cursor lands on after tabbing through the other fields -- matching the convention used by TextMate, LSP, VS Code, and others. It was treated as plain field 0 and sorted first, so a snippet like `foo(${1:bar})${0}` selected the empty `${0}` instead of `bar`. This orders `${0}` after every other field (numbered and named), so the first real placeholder is selected and `${0}` becomes the exit. Documented in the `snippet` docstring; test added.

ondrejmirtes added 1 commit

2026-05-22 09:17:23 +02:00

Treat ${0} as the final snippet tab stop 94ceb537d3

Snippet field order is by number, but ${0} should be the exit stop -- the
position the cursor lands on after tabbing through the other fields -- to match
the convention used by TextMate, LSP, VS Code, and others. It was sorted first
(as field 0), so a snippet like foo(${1:bar})${0} selected the empty ${0}
instead of bar. Order ${0} after every other field.