Life support?

[airgap]

P10k is now on life support? I am sad.

[runofthemillgeek]

Came here to look into an issue I had and saw the message. Hope everything's OK, @romkatv.

[henderea]

Are there any plans for a future version? And will pull requests be applied if anyone wants to fix a bug or add a feature?

[romkatv]

I have no plans for future versions or for new features. I won't be replying to requests for help, which encompass well over 90% of all issues I receive. I won't be merging PRs except those rare ones that can be merged as-is. I won't be fixing bugs other than in exceptional circumstances.

That said, I am using powerlevel10k myself and intend to continue using it. I won't be breaking powerlevel10k and I don't expect it to break on its own. It's not the kind of software that requires active maintenance just to keep working. If it works now for you, it'll keep working.

[moritzdietz]

I'm sorry you had to make this choice and I respect it. Hope you're doing well and if not, hope you will get better.

[romkatv]

I appreciate your concerns for my wellbeing. I am well by any objective and subjective measure.

[grimm26]

I just want to rip out gitstatus and replace with just vcs_info and git status. I've started looking at it, but I need to figure out how to untangle the web :)

[romkatv]

You don't have to "rip out" anything. There is a public API for custom prompt segments. See p10k help segment.

[grimm26]

so just write a new prompt segment that doesn't use gitstatus. I guess that's easier than converting the existing one :)

[Syphdias]

I'm curious: Why do you not want to use vcs?
If this is purely about the "life support" "issue", I'd encourage you to subscribe to all notifications of this repo. Roman is anything but inactive and helpful where ever he can.

[grimm26]

what I want is to excise gitstatus - as does Roman. Roman has indicated that he is pretty much done with all of this, though, so I will forge ahead as you do with an open source project.

[romkatv]

I want to have a fast backend for vcs segment that does not rely on gitstatusd. This will allow me to stop supporting gitstatusd, which is quite costly given that git is constantly evolving.

Note that vcs already has a slow backend based on vcs_info. You can enable it with POWERLEVEL9K_DISABLE_GITSTATUS=true. I don't think you'll gain anything by doing it but you'll definitely feel the slowdown.

[grimm26]

I don't really notice the slowdown but I don't like the default styling/format. I'll see about trying to match what I have with gitstatus. I gain not having to rely on gitstatus and having 10 or 20 of those processes hanging around as I work through the day.

[romkatv]

I gain not having to rely on gitstatus and having 10 or 20 of those processes hanging around as I work through the day.

The alternative to keeping processes hanging around is to fork and terminate them on each command, which is exactly what vcs_info does. It's wasteful of resources.

Think of it this way. If you are actively using a shell, gitstatusd saves resources by not having to fork and terminate a bunch of processes on every command. If you aren't actively using a shell, gitstatusd is idle, and thus using virtually no resources.

If your concern is efficiency, replacing gitstatus with vcs_info would be counterproductive.