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

Create zsh completion to pocok #33

Open
oak2 opened this issue Mar 18, 2018 · 2 comments
Open

Create zsh completion to pocok #33

oak2 opened this issue Mar 18, 2018 · 2 comments
Assignees

Comments

@oak2
Copy link

oak2 commented Mar 18, 2018

A zsh command completion would be great to pocok.

Here is a complete guide and a video about function:
https://github.com/zsh-users/zsh-completions
https://www.youtube.com/watch?v=E2WXc3qAg8A

@sarkiroka
Copy link
Contributor

I have same request for bash

Example:
proco up s<TAB> when only one project starts with "s" complete the command

proco up s<TAB><TAB> when more projects starts with "s" then two tab list all project which starts with "s"

@gaborkolarovics gaborkolarovics self-assigned this Mar 22, 2021
@sarkiroka
Copy link
Contributor

sarkiroka commented Mar 22, 2021

there are multiple autocomplete spaces, and multiple shells with separate syntax. therefore, it could be better if the poco could only provide the data easily for these shells.
what would be needed:

  • list of basic poco commands (up, down, help, etc.)
  • project names stored in catalogs - here and for others, it would be very important to return them immediately, do not wait for the result of the git pull only if there has never been such a result
  • what plan names there are in a given project
    more importantly, these names in the above three categories contain only the words to be completed and should be quick.
    I can imagine something like poco completion <commands | projects> and poco completion xyproject plans

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants