Missing completions

[elviskahoro]

See #654

[elviskahoro]

Support Kubectl

From @uhinze via #129

I'm relying heavily on kubectl in my day-to-day work. I normally use iTerm2 with oh-my-zsh with the kubectl plugin, which also gives me a k alias for kubectl and a bunch of others (like keti for kubectl exec -ti) which are super helpful. This would be awesome to have replicated in some way in Warp.
To explain a bit for non k8s users, when you're operating stuff on Kubernetes you need kubectl all the time. When you're deep into troubleshooting an issue, you may issue the command like 20/30/40 times in a row. So every keystroke less is good :-) the oh-my-zsh plugin solves this pretty well I think.
Maybe for Warp, this just means also autocompleting after resolving aliases (and not just for the blank kubectl command).

[elviskahoro]

From @joscdk via #129

Would like to add to this, for example by adding something like kube-ps1, so being able to show current K8s context and namespace just like git info.

Kube-ps1: https://github.com/jonmosco/kube-ps1

[elviskahoro]

From Nirlep via Discord: https://discord.com/channels/851854972600451112/932083406840410152/932802271367008257

@Elvis I can see that but what I was asking is... kubectl completion for kubernetes resources as well.

For example: kubectl describe pod - right now I can't auto/tab complete command after "describe" in Warp. It works in iTerm.

[elviskahoro]

https://k9scli.io/

[elviskahoro]

Tab completion for Azure CLI

From @robinhultman via #244

Describe the solution you'd like?

I would love to have tab completion for the Azure CLI

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

[kubblai]

second this plus awscli pls

[Bandgren]

same!

[elviskahoro]

Support MacPorts

From @Gregory-Gelfond via #343

Describe the solution you'd like?

Ideally we could have support for completions of `port` and `brew` provided by the [MacPorts](https://www.macports.org) and [HomeBrew](https://brew.sh) package management projects respectively.

Is your feature request related to a problem? Please describe.

No response

Additional context

No response

[elviskahoro]

From @Gregory-Gelfond

Maybe even parse a command's manpage to learn it's command completions and options.

[elviskahoro]

we added brew but haven't added macport yet

[elviskahoro]

Support for kubectx:

• Moved to #652: Support Kubectx #457

[spencercjh]

Figure 1 shows a screenshot in Kitty where I was able to list all the k8s CRDs starting with "po" using the "Tab" key. As shown in Figure 2, I can't do that in Warp, only “Postman” is listed (a folder in the current directory).

I wonder if I got something wrong that caused such a difference and imperfection

[snap10]

+1 to this, having the same issue

[elviskahoro]

Would like to have Oracle's SQLcl and OCI CLI

[d12bb]

Vim / Neovim

> cat /opt/homebrew/share/fish/completions/nvim.fish
complete -c nvim -w vim
# -> mostly the same 🤷🏼‍♂️

[paynecodes]

Some of my completions are only working after I run reload.

For example, knative cli and azure cli each have this issue.

---

Relevant .zshrc config for knative cli

# Add zsh completions for `kn` (knati`ve` cli)
source <(kn completion zsh)
compdef _kn kn

kn completion zsh output

#compdef _kn kn

# zsh completion for kn                                   -*- shell-script -*-

__kn_debug()
{
    local file="$BASH_COMP_DEBUG_FILE"
    if [[ -n ${file} ]]; then
        echo "$*" >> "${file}"
    fi
}

_kn()
{
    local shellCompDirectiveError=1
    local shellCompDirectiveNoSpace=2
    local shellCompDirectiveNoFileComp=4
    local shellCompDirectiveFilterFileExt=8
    local shellCompDirectiveFilterDirs=16

    local lastParam lastChar flagPrefix requestComp out directive comp lastComp noSpace
    local -a completions

    __kn_debug "\n========= starting completion logic =========="
    __kn_debug "CURRENT: ${CURRENT}, words[*]: ${words[*]}"

    # The user could have moved the cursor backwards on the command-line.
    # We need to trigger completion from the $CURRENT location, so we need
    # to truncate the command-line ($words) up to the $CURRENT location.
    # (We cannot use $CURSOR as its value does not work when a command is an alias.)
    words=("${=words[1,CURRENT]}")
    __kn_debug "Truncated words[*]: ${words[*]},"

    lastParam=${words[-1]}
    lastChar=${lastParam[-1]}
    __kn_debug "lastParam: ${lastParam}, lastChar: ${lastChar}"

    # For zsh, when completing a flag with an = (e.g., kn -n=<TAB>)
    # completions must be prefixed with the flag
    setopt local_options BASH_REMATCH
    if [[ "${lastParam}" =~ '-.*=' ]]; then
        # We are dealing with a flag with an =
        flagPrefix="-P ${BASH_REMATCH}"
    fi

    # Prepare the command to obtain completions
    requestComp="${words[1]} __complete ${words[2,-1]}"
    if [ "${lastChar}" = "" ]; then
        # If the last parameter is complete (there is a space following it)
        # We add an extra empty parameter so we can indicate this to the go completion code.
        __kn_debug "Adding extra empty parameter"
        requestComp="${requestComp} \"\""
    fi

    __kn_debug "About to call: eval ${requestComp}"

    # Use eval to handle any environment variables and such
    out=$(eval ${requestComp} 2>/dev/null)
    __kn_debug "completion output: ${out}"

    # Extract the directive integer following a : from the last line
    local lastLine
    while IFS='\n' read -r line; do
        lastLine=${line}
    done < <(printf "%s\n" "${out[@]}")
    __kn_debug "last line: ${lastLine}"

    if [ "${lastLine[1]}" = : ]; then
        directive=${lastLine[2,-1]}
        # Remove the directive including the : and the newline
        local suffix
        (( suffix=${#lastLine}+2))
        out=${out[1,-$suffix]}
    else
        # There is no directive specified.  Leave $out as is.
        __kn_debug "No directive found.  Setting do default"
        directive=0
    fi

    __kn_debug "directive: ${directive}"
    __kn_debug "completions: ${out}"
    __kn_debug "flagPrefix: ${flagPrefix}"

    if [ $((directive & shellCompDirectiveError)) -ne 0 ]; then
        __kn_debug "Completion received error. Ignoring completions."
        return
    fi

    while IFS='\n' read -r comp; do
        if [ -n "$comp" ]; then
            # If requested, completions are returned with a description.
            # The description is preceded by a TAB character.
            # For zsh's _describe, we need to use a : instead of a TAB.
            # We first need to escape any : as part of the completion itself.
            comp=${comp//:/\\:}

            local tab=$(printf '\t')
            comp=${comp//$tab/:}

            __kn_debug "Adding completion: ${comp}"
            completions+=${comp}
            lastComp=$comp
        fi
    done < <(printf "%s\n" "${out[@]}")

    if [ $((directive & shellCompDirectiveNoSpace)) -ne 0 ]; then
        __kn_debug "Activating nospace."
        noSpace="-S ''"
    fi

    if [ $((directive & shellCompDirectiveFilterFileExt)) -ne 0 ]; then
        # File extension filtering
        local filteringCmd
        filteringCmd='_files'
        for filter in ${completions[@]}; do
            if [ ${filter[1]} != '*' ]; then
                # zsh requires a glob pattern to do file filtering
                filter="\*.$filter"
            fi
            filteringCmd+=" -g $filter"
        done
        filteringCmd+=" ${flagPrefix}"

        __kn_debug "File filtering command: $filteringCmd"
        _arguments '*:filename:'"$filteringCmd"
    elif [ $((directive & shellCompDirectiveFilterDirs)) -ne 0 ]; then
        # File completion for directories only
        local subDir
        subdir="${completions[1]}"
        if [ -n "$subdir" ]; then
            __kn_debug "Listing directories in $subdir"
            pushd "${subdir}" >/dev/null 2>&1
        else
            __kn_debug "Listing directories in ."
        fi

        local result
        _arguments '*:dirname:_files -/'" ${flagPrefix}"
        result=$?
        if [ -n "$subdir" ]; then
            popd >/dev/null 2>&1
        fi
        return $result
    else
        __kn_debug "Calling _describe"
        if eval _describe "completions" completions $flagPrefix $noSpace; then
            __kn_debug "_describe found some completions"

            # Return the success of having called _describe
            return 0
        else
            __kn_debug "_describe did not find completions."
            __kn_debug "Checking if we should do file completion."
            if [ $((directive & shellCompDirectiveNoFileComp)) -ne 0 ]; then
                __kn_debug "deactivating file completion"

                # We must return an error code here to let zsh know that there were no
                # completions found by _describe; this is what will trigger other
                # matching algorithms to attempt to find completions.
                # For example zsh can match letters in the middle of words.
                return 1
            else
                # Perform file completion
                __kn_debug "Activating file completion"

                # We must return the result of this command, so it must be the
                # last command, or else we must store its result to return it.
                _arguments '*:filename:_files'" ${flagPrefix}"
            fi
        fi
    fi
}

# don't run the completion function when being source-ed or eval-ed
if [ "$funcstack[1]" = "_kn" ]; then
	_kn
fi

[elviskahoro]

I have a custom command and have setup completion for it using COMPREPLY
The completion works fine on normal terminal, but doesn't work on Warp. Does this require additional configuration to work?

[elviskahoro]

Should add support for these:
https://github.com/posener/complete/tree/master

[mlhynfield]

Hi, I would love to see 1Password CLI 2 tab completion.

I use op a lot, so a feature like this would be great.

[clo4]

I've added support for this to Fig now, so when the completions are updated in Warp you'll get op completions!

[clo4]

Completions in warp are updated now, new op completions available!

[zxiiro]

I would love to see fuzzy auto-complete supported as it is a feature I use extensively in my shell and is my current dealbreaker for using Warp.dev. For example let's say there's a directory called "github.com" the command cd hub<tab> should auto-complete to cd github.com.

[apie-takaie]

With the default font (Hack), the history is displayed with the ↑ command, but with other fonts, the history display is blank.
We have checked a number of fonts, but the same phenomenon occurs in all of them.
The attached image shows Lantighe TC.

[ricardopieper]

The AI command search is fantastic, but I have a suggestion to possibly improve it.

If I type "compile this project" in a Rust project folder (cargo), it tries to build a java program. If I type "compile this rust project" then it works. The AI could detect the existence of common project definition files (cargo, cmake, gradle, npm, yarn, maven, etc) and use it as a hint.

[mickeyperlstein]

thats not how ai works

[bartvdbraak]

@mickeyperlstein Actually, what @ricardopieper is suggesting could definitely work. Since Warp has context info about the current working directory, it could actually grab all file(type)s on that directory and pass that information into the prompt for the LLM. So even a basic question like Compile this would in turn be transformed to the following prompt (by Warp)

Compile this

For some context, here are the files in my current working directory: 
- Cargo.toml
- Cargo.lock
- .gitignore
- build.rs
- READM.md

As an example, I ran this with ChatGPT and got the following response:

Show answer

I'm sorry, but as an AI language model, I don't have the capability to directly compile code or interact with your local file system. However, I can provide you with some general information about compilation and the file types you mentioned.

• Cargo.toml: This file is used in Rust programming language projects and contains metadata about the project and its dependencies.
• Cargo.lock: This file is automatically generated by Cargo, the package manager for Rust, and it locks the version of dependencies used in the project to ensure consistency across different environments.
• .gitignore: This file is used with version control systems like Git and specifies which files and directories should be ignored and not tracked by the version control system.
• build.rs: This file is a build script used in Rust projects to perform pre-build tasks or set up the build environment.
• README.md: This is a Markdown file commonly used to provide documentation and information about the project.

If you have a Rust project and want to compile it, you can use the cargo command in your terminal. Make sure you have Rust and Cargo installed on your system. Then navigate to your project directory in the terminal and run:

cargo build

This command will compile the project and its dependencies. If there are no errors, the executable should be located in the target/debug/ directory (or target/release/ for a release build).

Keep in mind that I can only provide general guidance and cannot perform any actions on your specific environment or code. If you encounter any issues or need further assistance, please provide more details, and I'll be glad to help!

[nayishan]

can choose a font but can not chose a regular one or a bond one , some font's bond is a disaster

[dannyneira]

#3840 mentioned missing completions for apt, especially when ssh into ubuntu servers.

[dannyneira]

adding fish_config to the list based on user feedback on discord

[dannyneira]

Adding micromamba as mentioned on #3885

[imans777]

I hope I'm writing this in the correct place. I've been working with kubectl autocompletion and have found several things missing in the process and I'll note them down here.

1. kubectl -n infra get <TAB>
   when you want to set the namespace right after kubectl command and then try to autocomplete the resource, it doesn't work and instead shows the files in my current directory.

2. kubectl --context neda@production get <TAB>
   similar to previous item, when setting context before getting resources, it doesn't work and shows files.

3. kubectl logs -f <TAB>
   when trying to get the logs (both with -f flag and without) it shows the k8s resources instead of pods.

4. kubectl rollout status <TAB>
   when trying to rollout, we must specify the type of resource first (sts, deploy, ds, etc.) and then write that resource name, but the autocomplete directly suggests the resource name, which doesn't work. the issue exists with other types of rollouts (history, pause, resume, etc.).

Thanks again for this great product.

[Pierre-Mike]

here side by side WARP vs terminal and the completion

It may use search

brew search micro 

[c4shdev]

I returned to Iterm.

• This problem has been going on for years and there seems to be no plans to resolve it. Warp is a great product, but not having the correct completion prevents me from enjoying using it.

[jason5ng32]

plus 1.

[wesbos]

Any plans to fix this? Supporting completions for 1-off tools isn't the move- if a CLI has this available, it should just work in Warp

[jason5ng32]

It's very inconvenient when you type: apt install ng [TAB] , and "nginx" not showing up.

[Dogacel]

Not supporting custom completion scripts is annoying. I already have some custom tooling that uses argcomplete to generate completions but unfortunately Warp doesn't allow me to add them 😠

[dscham]

Coming in with wanting the autocompletions from the shell to work correctly.

But I rather ask what needs to be done for this to work, or a direction to look in? I mean, why just complain if you could possibly change it yourself. That's what OSS is for, right?

[wesbos]

Warp isn't open source - at least not yet. If passing through completions doesnt work, they could make the completions open source so the community can maintain. Might even be a better experience, similar to how Fig completions worked

[ubamrein]

There have been multiple suggestions - in this discussion - on how the community could help - and a lot of people offered to implement the auto-completion for their needed tools themselves -, but so far they only promised but did not open source the spec.

I'm honestly a bit disappointed, since I love using the editor like CLI, but I barely use all the AI features they seemed to be focus on, and the one thing, people who are regularly using the terminal need - working auto-completion -, is just being ignored.

[dscham]

Warp isn't open source - at least not yet. If passing through completions doesnt work, they could make the completions open source so the community can maintain. Might even be a better experience, similar to how Fig completions worked

Wait what? I didn't realize.

I hope they are at least paying for using Github then. Would be a real di** move to use it for issues but not giving the source out imho.

[plinkplinkfizz]

You don't have to worry about Github. They are far from ethical.

Also, hoping our sensitive information is not leaving our systems. Throwing out Warp until it is open-sourced.

[excieve]

Please add support for dnf and yum package management tools completion on Linux.

[excieve]

And for that matter flatpak too. They should all be able to complete installed/installable packages depending on the context.

[neilbags]

Great work in releasing the Linux version today. It seems I can't cd into a folder that is a symlink. This is very unintuitive. Is this something that was done on purpose? an oversight, or something that has not been implemented yet?

[t40mas]

Please add podman directly. Aliases sometimes do not work.
And yadm https://github.com/TheLocehiliosan/yadm ☺️

[mattheworris]

[wesbos]

This should already exist - its one of the few well supported completions

[schabrolles]

If possible, add oc (openshift-client) which is very close to kubectl