Files
task/internal
Valentin Maerten 13f72a0b56 fix(completion): always leave a trailing space after a task name
The protocol carries one directive per response, so a single truncated wildcard prefix cost every complete name its trailing space: a Taskfile holding `deploy-*` anywhere made `task buil<TAB>` insert `build` with the cursor stuck against it. Completing a task name is the common case and the wildcard prefix the rare one, so the polarity was backwards — and the legacy wrappers, which had no notion of an incomplete candidate, always left the space.

A wildcard prefix now gets a space it does not want, which is the accepted trade until suggestions can carry a directive of their own. Required variables keep NoSpace: there a free-form `VAR=` is the common case, not the exception.
2026-08-20 16:51:59 +02:00
..
2025-09-11 10:26:59 +01:00
2026-08-18 17:23:38 +02:00