Folder Autocomplete not working

[rafael]

Discord username (optional)

No response

Describe the bug

Folder auto-complete doesn't seem to be behaving in the same way as the normal terminal. I'm not sure what's wrong with my setup because for a colleague it seems to be working correctly. When starting to to type a folder name, I would expect to auto-complete the deterministic portion and when tapping TAB it shows me the options of the folders that will help disambiguate. In warp I'm seeing:

There are no options to see folder_a, folder_b, folder_c it just autocompletes to a.

To Reproduce

Steps

1. Create a folder with three folders inside: folder_a, folder_b, folder_c.
2. Type cd f
3. In my setup just autocompletes to folder_a. There are no options to choose the other folders.

Expected behavior

When starting to to type a folder name, I would expect to auto-complete the deterministic portion and when tapping TAB it shows me the options of the folders that will help disambiguate. E.g:

Screenshots

No response

Operating System

MacOS

Operating System and Version

MacOS Monterey 12.3.1

Shell Version

zsh 5.8 (x86_64-apple-darwin21.0)

Warp Version

v0.2023.03.07.08.02.stable_01

Additional context

I'm using oh-my-zsh. Not sure if that could be creating some problems.

Does this block you from using Warp daily?

No

Is this a Warp specific issue? (i.e. does it happen in Terminal, iTerm, Kitty, etc.)

Yes, this I confirmed this only happens in Warp, not other terminals.

Warp Internal (ignore): linear-label:b8107fdf-ba31-488d-b103-d271c89cac3e

None

[dannyneira]

Hi @rafael Sorry about this issue, but I can't seem to reproduce the behavior. In Warp, when you press TAB, it should bring up the completion menu, so it may be the case that you're using an unsupported oh-my-zsh plugin that is preventing this behavior.

My guess is that you normally have a custom prompt, theme, or plugin and Warp is unable to parse it.

You can check whether it’s something in your dotfiles by setting up clean configs: Run echo 'ZDOTDIR=/' > ~/.zshenv This forces Zsh to run with zero configs.

You can disable parts of your dotfiles just for Warp by using this conditional statement:

# Bash and Zsh
if [[ $TERM_PROGRAM != "WarpTerminal" ]]; then
# > What you want to disable here <
fi

We have a list of incompatible tools here: https://docs.warp.dev/help/known-issues#list-of-incompatible-tools And more info on custom prompts here: https://docs.warp.dev/features/prompt

[dannyneira]

any luck @rafael ?

[dannyneira]

Closing as we can't reproduce and there appears to be no response. Please let us know if the issue persists.

[rafaelfigma]

Oh sorry, I did not get a chance to come back to this until now. I tried starting with zero configs and I still see the issue. The only workaround I've bound so far is to start a new shell within the shell. Then it starts working :(

[dannyneira]

Thanks for the followup, please try the following:

• run which zsh
• put the result of that command into Warp > Settings > Session > Startup shell for new sessions > Custom. (in my example zsh is located in /opt/homebrew/bin/zsh, but yours may be different)

[rafael]

Sorry for the slowest feedback loop here. This is something that still happens for me both in my personal and work laptop :(

I feel like something simple must be off that I'm missing. Here a loom video showing the behavior: https://www.loom.com/share/769c62cfe07e49b99da0253f998e835e?sid=4dfe0c13-63fe-4f8c-a9d2-98d1acdd7b29

I notice that this is also happens in bash. In the video, this is a super vanilla bash terminal with no customization and still runs into the problem.

[rafael]

Hey @dannyneira - sorry to keep coming to this. I still haven't been able to figure out this issue. I've tried what you suggested here, but no luck.

What could be the best way to follow up here?