-
Notifications
You must be signed in to change notification settings - Fork 2.3k
'asdf current' output has changed #2849
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
Comments
Thanks for reporting this, and so clearly, too! I'll take a look. I'm maintaining Powerlevel10k. It still works as intended and I'm keeping it that way. I don't do user support, or at least not nearly as much as before, and I don't implement new features. |
No problem, and thanks, I appreciate your work. I dabbled with starship but its just not the same ha. fyi, it looks like they also removed |
Yes, that should be clear to anyone who codes. Starship has a sleek website and honestly great docs. It's easy to set up and customize, which makes it attractive to many zsh users. The only real downside is that the prompt itself isn't as good as p10k. Most won't notice, and those who could tell usually don't try both. |
Apologies, you can probably close this. I'm not so sure this is actually broken. The comments in the config file made me think that p10k executes and parses Basically I wasn't seeing python version when changing into a python dir with the version in .tool-versions. However I see that it does appear when I make local the version different from global version (~/.tool-versions). My setting =
Example of python version not appearing when local == global
|
I might be too sleepy to understand your message properly right now, but does this illuminate?
|
Yea those code comments seem to indicate that if POWERLEVEL9K_ASDF_SOURCES contains 'local' then the tool version WILL be shown even if local version == global version. So for my setup: But python version is NOT shown in the prompt when in the project dir (local) until I make it different from the global version. It does appear to be a bug but I'm not sure that it's related to the asdf v0.16 changes |
The comments indicate something close to what you are inferring but not quite that. The last comment I quoted shows an example of the same situation you are encountering. |
Ok, I understand, at first the 2 statements seem contradictory:
But actually they relate to 2 completely separate settings. Updating my config to the below setting makes it work as I expected.
Closing, sorry this turned into user support 😅 |
No worries! The names of these parameters aren't intuitive, and the interactions between them are complex. The docs are precise though. This combination is quite common when it comes to p10k configuration. |
Uh oh!
There was an error while loading. Please reload this page.
I know this project is no longer being maintained, reporting so others can find the issue. ASDF made breaking changes in v0.16.0
https://asdf-vm.com/guide/upgrading-to-v0-16.html#breaking-changes
This negatively affects
typeset -g POWERLEVEL9K_ASDF_SOURCES=(shell local global)
since the expected output no longer matchThe text was updated successfully, but these errors were encountered: