Open mentasuave01 opened 4 months ago
Hi @mentasuave01 thanks for reporting. What's the other terminal in this screenshot? Is it GNOME terminal? Is it running bash as a non-login shell? Warp does run bash as a login shell. So, it's possible you need to add to your PATH inside ~/.bash_profile
instead. Personally, I include this snippet in my ~/.bash_profile
to ensure everything in my ~/.bashrc
gets run for login and non-login shells:
[ -f ~/.bashrc ] && source ~/.bashrc
We should also make sure that Warp is selecting the right shell. Can you run this command in both terminals and post the output?
$SHELL --version
You can also confirm if bun
is being registered by running which bun
which should print out the binaries directory/location.
@mentasuave01 any luck with the suggestions above?
Dupe Check
Describe the bug
To reproduce
Open warp terminal and call bun, bun path is registered in ~/.bashrc
Expected behavior
No response
Screenshots
No response
Operating system
Linux
Operating system and version
Ubuntu 22.04
Shell Version
5.1.16
Current Warp version
v0.2024.04.23.08.01.stable_03
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?
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