Open laserjim opened 3 months ago
Thanks for letting us know @laserjim Thanks for letting us know. I was able to reproduce this issue. As a workaround you can add a space after the =
but before the /Use
and Warp should open the completions menu correctly. I'll notify the team and we'll post any updates on this thread.
To anyone else facing this issue, please add a 👍 to the original post at the top or comment with your details, and subscribe if you'd like to be notified.
Hello, I have a similar issue on Linux using zsh. During a session, when the PATH variable is modified the completion doesn't take that into account. On my case, it is a usefull feature when using Python environment...
Do you have a fix for that on Linux?
Dupe Check
Describe the bug
Autocomplete fails to complete path when setting environment variable.
To reproduce
On a mac, type "export PATH=/Use" and then hit tab to complete. Notice that the terminal won't attempt an autocomplete.
Expected behavior
A standard file autocomplete, offering to complete "export PATH=/Users/".
Screenshots
No response
Operating system
MacOS
Operating system and version
OS X
Shell Version
bash
Current Warp version
No response
Regression
No, this bug or issue has existed throughout my experience using Warp
Recent working Warp date
No response
Additional context
No response
Does this block you from using Warp daily?
No
Is this an issue only in Warp?
Yes, I confirmed that this only happens in Warp, not other terminals.
Warp Internal (ignore): linear-label:b9d78064-c89e-4973-b153-5178a31ee54e
None