Autocomplete doesn't work on commands that autocompletes on demand or dynamically

[JuanDGiraldoM]

Discord username (optional)

No response

Describe the bug

Autocomplete doesn't works when you try to autocomplete on commands that doesn't have a predefined behaviour like sdk or git

Sdkman for sample, list all the available versions

But from Warp (using or not default prompt), try to autocomplete from directory

Git for sample, list all available branches

But from Warp, just list the used before

To Reproduce

With sdkman, just install from https://sdkman.io/

And try to install some tool like gradle, java or maven. Using version autocomplete (double tab before specify any version)

Ex.

With git, just use a repository with many branches, and try swith to another using autocomplete branch name

Expected behavior

Autocomplete right options

With sdkman, all available versions

With git, all available branches

Screenshots

With iTerm

With Warp

Operating System

MacOS

OS Version

13.2.1

Shell Version

zsh 5.8.1 (x86_64-apple-darwin22.0)

Warp Version

v0.2023.04.04.08.03.stable_01

Additional context

No response

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

[JuanDGiraldoM]

The same applies to aws cli

It doen't autocomplete

Like this

[dannyneira]

Appreciate you submitting this @JuanDGiraldoM Some of these we should at least partially support: https://docs.warp.dev/features/completions#supported-completion-specs

We'll post any updates on this thread.

Also, we have a relevant discussion tracking missing completions here: #652

[aromanov-pix]

This is actually blocking me from using Warp terminal because completion doesn't work in most demanded tools like git, aws cli, gcloud, kubectl, etc...

[ansromanov]

@dannyneira I reviewed supported completion specs table, and according to it kubectl should have full completion support. But it is not true at the moment:

I check with latest stable version v0.2023.05.30.08.03.stable_02

[matheusmaais]

same here, autocomplete for zsh not work on warp but it does in iterm2, so it would be nice get this feature

[ossfellow]

Appreciate you submitting this @JuanDGiraldoM Some of these we should at least partially support: https://docs.warp.dev/features/completions#supported-completion-specs

We'll post any updates on this thread.

Also, we have a relevant discussion tracking missing completions here: #652

@dannyneira, I'm not sure what rationales are behind building auto completions into the product; but it's logical to assume it's a losing battle, given that more new tools will appear, each offering their own scripted completions, which could be added to the user shell. We each use the tools we need to mange our work, and right now Warp's auto-completion system is totally broken for many of us. Could you at least please clarify why the legacy (if you like to call it) model of tool completions cannot be supported?

[dannyneira]

@masoudbahar It mainly has to do with the input editor wrapper, which enables the IDE-like experience. Unlike other terminals, we've had to implement our own input so the completions that work with other terminals don't work with Warp for that reason. We do have plans to improve completions and possibly create extensions/APIs so that the community can contribute to our completion specs or some other better solution for the longer term (possibly porting existing completion specs which we currently do with Figs open source completions for example).

[ossfellow]

Thanks for clarifying the reason. Warp by far is the best terminal application I’ve used; but quite frankly, the lack of this feature is very frustrating for someone like me, who spends considerable time every day working in that environment. Hopefully the long term plans for adding the extension system wouldn’t turn to years.

[marv070]

@dannyneira I reviewed supported completion specs table, and according to it kubectl should have full completion support. But it is not true at the moment:

I check with latest stable version v0.2023.05.30.08.03.stable_02

I unfortunately am seeing the same for version v0.2023.08.01.08.05.stable_02

[shdobxr]

Also concur more of the same, <3 warp, but this inability to work with AWS CLI completion is making me sad.

[pentacore]

Still seeing this issue, and it might well be a deal breaker

[seifrajhi]

It is unfortunate that this cool tool does not yet support autocompletion for commonly used tools such as git, aws cli, gcloud, and kubectl, helm, terraform, etc 😞 I cannot fully migrate to warp unless this is supported.

[elichai]

I've been happily using warp for a few months now, but now I need to use a few cloud tools and autocompletion there is very important for beginners, and I just now realized it actually never worked :(

[rohitpelago]

Same here., docker compose autocompletes also doesn't work. When I try to ran docker compose up <service> it doesn't show available service names.

[danielpertinence]

Same here. Keep up the good work still