Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Commands autocompletion is not working #9335

Closed
satrox28 opened this issue Apr 7, 2023 · 8 comments
Closed

Commands autocompletion is not working #9335

satrox28 opened this issue Apr 7, 2023 · 8 comments
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.

Comments

@satrox28
Copy link

satrox28 commented Apr 7, 2023

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 #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 satrox28 changed the title Autocompletion not working Commands autocompletion is not working Apr 7, 2023
@satrox28
Copy link
Author

satrox28 commented Apr 12, 2023

Hi Team,

Is there any solution @starpit

@starpit
Copy link
Contributor

starpit commented Apr 12, 2023

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
Copy link

jorpilo commented Jul 5, 2023

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

@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 23, 2024
@k8s-triage-robot
Copy link

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-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 22, 2024
@Dessix
Copy link

Dessix commented Mar 10, 2024

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
Copy link

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-ci-robot
Copy link

@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 k8s-ci-robot closed this as not planned Won't fix, can't repro, duplicate, stale Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed.
Projects
None yet
Development

No branches or pull requests

6 participants