Suggestion: Migrate from Powerlevel10k to Starship.rs or Oh My Posh

[prime-run]

Currently, the project uses Powerlevel10k, which has the following explicitly stated in its README(life support!):

• Very limited support
• No new features are in the works
• Most bugs will go unfixed
• Help requests will be ignored

Given these constraints, I suggest migrating to an alternative like Starship.rs or Oh My Posh. Both are modern, faster, and more configurable prompt tools that support multiple configurations. This would allow for:

• Improved performance: Both alternatives are generally faster than Powerlevel10k.
• Greater flexibility: Multi-config support would enable seamless integration with wallbash.
• Active development and support: These tools are actively maintained, ensuring better responsiveness to issues and feature requests.

This migration could enhance the overall user experience and maintainability of the project. Let me know your thoughts!

P.S: personally, I suggest Starship

[kRHYME7]

P.S: personally, I suggest Starship

I am currently using Starship but I usually use OMP on several installs I had. Both in vanilla.

So I am expecting both can do multi file configuration?
Which one is the easiest to implement?

[prime-run]

I feel it's gonna be a long thread!
How about I open a PR instead? 😁

[kRHYME7]

yeah let's move there.

[prime-run]

@kRHYME7
First please let me clarify, by:

Multi-config support

I meant we can have multiple single-file configurations with custom names and choose which one to evaluate for each instance without any scripts.

So now my question is: Do we want something like colors.toml alongside our starship config.toml? The alternative is having the theme engine configure all our starship config files on, e.g., a "global wallpaper change", which can get nasty! Or, we could just give up on theming it and have a few default configurations (for non-power users).

My solution if we want colors.toml: As you know, since the TOML parser doesn't allow reading other files, it's not as straightforward as sourcing colors*.toml in the main config. There are easy workarounds, of course. But in that case, I might as well make a simple setup CLI tool similar to p10k configure so that users can choose all other options as well. We can even test for font and spacing issues, just like p10k.

Please let me know your thoughts!

P.S: I can do it in go or rust; I refuse to do it in bash :)

[kRHYME7]

Or, we could just give up on theming it

I'm on this side Right now. I can't represent the whole user base but changing the prompt now and then is too confusing for me. There's no point in doing so. It's cool but I don't know if it's worth the effort.

Though I'm sure that we can modify the color dynamically if it's a toml file.

I made a write_toml function which uses kwriteconfig from kde, which modifies a toml file. So I don't know if we needed a separate program to inject/modify a toml config in this repo.

[kRHYME7]

We can also ask starship repo to add multi file configuration.

And BTW, why is this + CLI not a feature in starship? yet? How about Oh My Posh?

[prime-run]

Regarding Oh My Posh, I suggest forgetting it! Sooner or later, we will have to migrate to starship because it's significantly more performant and completely unopinionated.

---

Why is this + CLI not a feature in starship yet?

I would assume it's because (unlike p10k) it's really easy to configure "everything"! That's why I said:

(for non-power users).

---

Though I'm sure that we can modify the color dynamically if it's a TOML file.

It's not just colors (though it's mostly colors 😄). Depending on the configuration and preset, the number of color values to set is different. For example, one preset uses different colors for each icon in the git status, while another uses the a single value for all of them!

---

I made a write_toml function which uses kwriteconfig from KDE, which modifies a TOML file. So I don't know if we need a separate program to inject/modify a TOML config in this repo.

Well, I suggested a "program" for an all-in-one solution needing time, testing, but if we want to change files rather than generating them, I believe a cleaner solution is to have a temporary styles.toml file, like:

[styles]
# --- General Styles ---
# common colors and/or text styles

for which we use write_toml to populate and then echo that to the main config on theme change!

[prime-run]

As of right now, I have fully migrated from p10k to starship.rs, and I have five configurations to choose from. I've also added documentation with references for further configurations.

I could stop here, do some testing, and open the first PR since we don't currently have the theming feature in p10k, which was my original goal when I opened this issue. However, after seeing what is possible with starship, I can't help but feel it would be a missed opportunity not to explore further.

In the future, we could even go as far as having a selector for it (the same as for wallpaper or theme!).

edited: please let me know your thoughts on how to proceed

[kRHYME7]

I see, let's make it simple for now. add the starship config as a PR. At least 1 config that you feel is suitable for general use. Don't remove p10k yet. I'll probably co author in the PR on how we can populate it properly.

Did you installed starship from AUR?

[prime-run]

please checkout preset(2) and preset(4) in #514 screenshot ,

You can see how ricable it can be and also how 2 doesn't really look good with my current setup and colors.

Did you installed starship from AUR?

@kRHYME7 I notice you added that from in AUR and you are sad dropping our old mate p10k 😄