-
-
Notifications
You must be signed in to change notification settings - Fork 631
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Starship with the current main branch: KeyError: 'obj' #5441
Comments
Hey! Nice catch! UPD: here: We have two ways: update starship or revert xonsh to "obj". I'm going to revert rename until we will have singleton for jobs to implement backwards compatibility. |
Sorry for forgetting to mention that. The command |
PR is here. Thanks! |
### Motivation Closes #5441 In the nutshell [Starship uses "obj"](https://github.com/starship/starship/blob/86c1312a05116fb404ab6ae90af37f78915f77b8/src/init/starship.xsh#L4-L11) so let's revert [the renaming](0f25a5a#diff-893f3d2e484910a3d1f57b499bdc81bf828ad764af9b7de0a8abb3d4e648d2c7L958) and will implement backwards compatibility when we switch jobs to singleton object some day. ## For community ⬇️ **Please click the 👍 reaction instead of leaving a `+1` or 👍 comment** Co-authored-by: a <1@1.1>
Current Behavior
On the latest git version of xonsh with starship enabled, after successfully capturing a subprocess, it shows the following traceback, and the starship prompt is temporarily gone until the next command is executed.
Traceback (if applicable):
I found this issue when investigating #5003, reproduced and bisected in my Arch Linux container. The first bad commit is 0f25a5a.
Expected Behavior
There shouldn't be any errors after using !(), and the starship prompt should show up as normal afterwards.
xonfig
For community
⬇️ Please click the 👍 reaction instead of leaving a
+1
or 👍 commentThe text was updated successfully, but these errors were encountered: