Open wilsonhou opened 7 months ago
Hi @wilsonhou sorry about this, please work around by putting the following alias in your rc file.
alias ~='cd ~'
thanks for the quick response danny! unfortunately not working as a workaround :(
^applied alias
same issue happening after alias applied and terminal restarted^
seems like it's getting confused about my current working directory location: (e.g it's suggesting folders that don't exist in the current directory:
weirdly enough, relative paths seem to get correct autocomplete, and even absolute paths? (starting with /
) - aliasing doesn't seem to help with autocomplete at all though unfortunately (e.g aliasing ~
with /Users/wilsonhou/
doesn't fix the autocomplete being broken issue.)
Just tested on v0.2024.03.05.08.02.stable_01
: issue exists in that release too.
This is an issue we're looking into. It looks like even with the workaround, we're getting permission denied errors.
Discord username (optional)
itswilsonhou
Describe the bug
Navigating between folders without
cd
has broken autocomplete / suggestions.E.g:
~/Documents/lowercase
-> this will show either 'No suggestions' or incorrect suggestionscd ~/Documents/lowercase
-> this will show correct suggestionsTo reproduce
Open warp's global terminal (with the global hotkey).
Try to navigate to any folder with
~/anything
-> autocomplete / suggestions should be broken.Expected behavior
I expect suggestions to come up instead of just saying 'No suggestions' or worse, incorrect suggestions.
Screenshots
Screenshot of 'No suggestions' when there should be suggestions.
Screenshot of nonsensical / wrong suggestions.
i don't even know what to say to this one^ 😅
Screenshot of correct suggestions when using
cd
explicitlyOperating system
MacOS
Operating system and version
Sonoma 14.0 (23A344)
Shell Version
zsh 5.9 (x86_64-apple-darwin23.0)
Current Warp version
v0.2024.03.12.08.02.stable_01
Regression
Yes, this bug started recently or with X Warp version.
Recent working Warp date
18/3/2024 ? (issue first experienced today: 19/3/2024), AEST timezone.
Additional context
Using oh-my-zsh if that helps. Very vanilla
.zshrc
file consisting of something like this:Does this block you from using Warp daily?
Yes, this issue prevents me from using Warp daily.
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:b9d78064-c89e-4973-b153-5178a31ee54e
None