kui icon indicating copy to clipboard operation
kui copied to clipboard

Commands autocompletion is not working

Open satrox28 opened this issue 2 years ago • 6 comments

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

  • Kui version: 13.1.3
  • Operating system: macOS 13.1/zsh

satrox28 avatar Apr 07 '23 10:04 satrox28

Hi Team,

Is there any solution @starpit

satrox28 avatar Apr 12 '23 09:04 satrox28

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!

starpit avatar Apr 12 '23 13:04 starpit

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

jorpilo avatar Jul 05 '23 04:07 jorpilo

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

This bot triages un-triaged 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:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle stale

k8s-triage-robot avatar Jan 23 '24 21:01 k8s-triage-robot

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:

  • 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:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Feb 22 '24 22:02 k8s-triage-robot

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.

Dessix avatar Mar 10 '24 23:03 Dessix

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

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

/close not-planned

k8s-triage-robot avatar Apr 10 '24 00:04 k8s-triage-robot

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

In response to this:

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

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

/close not-planned

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

k8s-ci-robot avatar Apr 10 '24 00:04 k8s-ci-robot