search

kubernetes-sigs / kui

A hybrid command-line/UI development experience for cloud-native development
Apache License 2.0
2.81k stars 183 forks source link

Commands autocompletion is not working #9335

Closed satrox28 closed 5 months ago

satrox28 commented 1 year ago

Describe the bug Autocompletion commands are not working on kui shell, have to type the full commands or copy/paste the commands.

Related to this issue https://github.com/kubernetes-sigs/kui/issues/2885

Steps to reproduce the behavior

  1. Type a command and press tab, doesn't show the autosuggestions/autocomplete.

Expected behavior The commands to autocomplete

System

satrox28 commented 1 year ago

Hi Team,

Is there any solution @starpit

starpit commented 1 year ago

hello! thanks for reporting this. could you add some commands that do not complete? i just tried kube<tab> g<tab> and got kubectl get 🤔

thanks!

jorpilo commented 1 year ago

is there any way that kubectl show possible commands without having to add 1 letter?

k8s-triage-robot commented 7 months ago

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

k8s-triage-robot commented 6 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

Dessix commented 6 months ago

This appears to be actively reproing still. Some items complete, while others do not.

Out of this command: kubectl get -n my-namespace pods kubectl, get, my-namespace were able to tab-complete, while pods failed to complete from po, and multiple tab keypresses resulted in the focus changing to the hamburger-menu of the UI, then along the tab bar, losing focus on the text entirely.

It appears that - if completion fails to produce meaningful results - the tab press rotates focus along the page in a destructive manner. Oddly, attempting to complete from the already-completed word pod suppresses the issue, retaining the focus as if it is completing to the one available option and absorbing the tab press.

k8s-triage-robot commented 5 months ago

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

You can:

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

k8s-ci-robot commented 5 months ago

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes-sigs/kui/issues/9335#issuecomment-2046234166): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages issues according to the following rules: >- After 90d of inactivity, `lifecycle/stale` is applied >- After 30d of inactivity since `lifecycle/stale` was applied, `lifecycle/rotten` is applied >- After 30d of inactivity since `lifecycle/rotten` was applied, the issue is closed > >You can: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.