Does it make sense to add space after command when auto-completing?

[pavelzherdin]

F.e., terraform does this: if you type in "terraform appl", and hit tab, it will finish the "apply" and add a space after it. AWS CLI does the same if it can. So typing "aws ec2" and then tab would do nothing, since ec2 is a prefix for more than one command.
Mise doesn't add that space, though. If I type "mise ru", it will get completed into "mise run", but the cursor stays at the "n".

Any reason not to add that space? Or could it be my shell that's doing this? I'm using bash.

-- edited:
Naturally, I figured out how to change this behavior after asking the question. Feel free to delete =)

[JamBalaya56562]

It is mise's completion rather than your shell. The generated bash completion registers with
-o nospace, which is exactly the flag that tells readline not to append a space.

Measured on v2026.8.3, bash 5.2:

$ eval "$(mise completion bash)"; complete -p mise
complete -o bashdefault -o nosort -o nospace -F _mise mise

The reason it is there: mise completes things meant to be continued rather than terminated —
mise use node@ wants a version appended, mise run build: wants the rest of a namespaced task
name. A trailing space would break both.

If you prefer the space everywhere, re-register after sourcing the completion:

eval "$(mise completion bash)"
complete -o bashdefault -o nosort -F _mise mise

$ complete -p mise
complete -o bashdefault -o nosort -F _mise mise

You trade away the node@ / build: continuation for it. Leaving this here rather than deleting
the thread, since it is the first place someone searching for this will land.