powerlevel10k support

[romkatv]

I'm the author and maintainer of powerlevel10k (a zsh theme). I see in the docs that Warp does not support powerlevel10k. Is there anything I can help you with?

I haven't used Warp but from other terminals with similar capabilities I gather that you need to annotate prompt and the command line with special escape codes. Powerlevel10k has built-in support for popular annotations. The right kind of annotation is enabled automatically based on the terminal (iTerm2, Kitty, VSCode, etc.). I could do the same for Warp but I would need to know what needs annotating. Perhaps you have a specification of the protocol?

Warp Internal (ignore) - linear-label:770f6576-d6c0-4e4f-a259-fc64b5156087

[trueblooda]

+1 This would be amazing. I would love to help too. (in whatever way I can)

[dannyneira]

Hi @romkatv Thanks so much for submitting this and your offer to help make Powerlevel10K work with Warp!
We have notified the engineers that worked on this, they are gathering the details and will respond on this thread.

Please add a :+1: to the original post at the top to signal that you want this feature, and hit the subscribe button if you'd like to be notified.

[marcosdipaolo]

Thanks @romkatv for helping, i'd love to have powerlevel10k working with warp asap!! 💪

[marcosdipaolo]

Any news from this? 🤔

[romkatv]

Closing as there doesn't seem to be any interest from the devs.

[vorporeal]

@romkatv Hey! We're definitely interested, and would love to work with you to get p10k working well within Warp. I'm so sorry that we haven't been more proactive about reaching out; we were trying to collect institutional knowledge about the issues we uncovered when investigating the p10k compatibility problem a long time ago, and then the person who was going to reach out went OOO.

Give me a couple days to build an up-to-date understanding of the specific issues that appear when trying to use Warp with p10k and I'll reply with them here.

In the meantime, can you link me to the part of the p10k codebase that adds the annotations you were mentioning? I can mentally map that onto what would make sense for Warp and be better able to make a suggestion about a path forward.

Again, really sorry that we dropped the ball here.

[romkatv]

No worries, I understand that things can be hectic in a fast-moving project.

If you search for "_POWERLEVEL9K_TERM_SHELL_INTEGRATION" within p10k.zsh, you'll find most of the shell integration code. This code is nearly impenetrable, which is why I offered to make changes to it myself.

Powerlevel10k has a few capabilities that might prove challenging to handle. Let me summarize them.

Prompt may change when you press ENTER

Here's an example where a multi-line prompt changes to a single-character prompt on ENTER.

Here prompt is contracted on ENTER but it can also expand. For example, some users like to have timestamps on past prompt commands without having the timestamp on the current prompt. In this case a timestamp is added to prompt when you press ENTER.

Prompt may change in response to what you are typing

Here's an example where prompt shows Google Cloud credentials and Kubernetes context when the command you are typing invokes gcloud or kubectl respectively.

Prompt may change on its own accord

Some prompt segments can update asynchronously. In practice this means that prompt may change on its own without any user action. This can lead both to contraction and expansion. In the extreme, even the height of prompt may change.

Prompt may change when the terminal window is resized

You most likely can already handle this because it's not unusual for zsh prompt to change on resize but I want to mention it for completeness. Here's an example (see the end of the recording):

Powerlevel10k may print a fake first prompt before zsh is initialized

This feature is meant to hide zsh initialization latency: instead of looking at an empty screen for some time after starting zsh, the user is instantly presented with a prompt and can start typing. When zsh is fully initialized, the fake prompt is replaced with the real thing.

In this example the real prompt looks the same as the fake prompt but it can also be different. For example, if the current directory is under a git repository, the fake prompt won't have git status but the real prompt will.

More info about this feature: https://github.com/romkatv/zsh-bench#instant-prompt

[vorporeal]

Hey @romkatv, one question for you while I work out a more complete technical design on our end:

I see that the escape sequence OSC 133 ; A ST is sent before the prompt contents, and OSC 133 ; B ST is sent after them. As far as I can tell, the right-side prompt is not included in this, and has no markers surrounding it. Would it be possible to introduce another pair of markers for the right-side prompt? I'm still doing some testing/prototyping on our end, but that might be the primary change needed on your end for things to work well.

[romkatv]

I can embed any escape sequence in any place within powerlevel10k prompt you like.

[vorporeal]

Fantastic. In my prototype (where I modified _p9k_prompt_prefix_right and _p9k_prompt_suffix_right to add markers), I'm noticing some odd artifacts in the right-side prompt:

Any immediate thoughts as to what might be going on?

Here's the small adjustment I made:

  if (( _POWERLEVEL9K_TERM_SHELL_INTEGRATION )); then
    _p9k_prompt_prefix_left+=$'%{\e]133;A\a%}'
    _p9k_prompt_suffix_left+=$'%{\e]133;B\a%}'
+   _p9k_prompt_prefix_right+=$'%{\e]133;C\a%}'
+   _p9k_prompt_suffix_right+=$'%{\e]133;D\a%}'

[romkatv]

If you tell me how you want prompt to be marked, I'll make the changes.

[vorporeal]

Sure; I can keep working on the necessary changes for broad functionality on our end and assume that the changes you make will address any small oddities I encounter.

I'll leave a more detailed comment either tomorrow or Monday with the set of changes that we'll need on the p10k end to address compatibility issues!