After entering a (or any other key):
┏[ hyoryu][ RAM: 28/63GB][ ~]\n┏[ hyoryu][ RAM: 28/63GB][ ~]\n┖[ 01:53:21] ♥ aThe creator of Oh My Posh cannot reproduce this issue, but I have been able to reproduce it on three different computers(I use GitHub to store the same set of configurations). I have no idea why this happens. Could anyone help me?
\nDetails are available at:
\nJanDeDobbeleer/oh-my-posh#5677
","upvoteCount":2,"answerCount":2,"acceptedAnswer":{"@type":"Answer","text":"I said this over at the omp repo too. This is what I think is going on, but I could be wrong.
\nThe only time i've seen something like this in nushell is when nushell starts too fast. As I recall, what happens is nushell starts and gets the terminal width, let's say 80x24, in the meantime, your terminal finishes starting and now the terminal width is 100x24, but nushell already knows the size as 80x24, so when you type any character, it realizes it's bigger and redraws the prompt. At least that's my theory. We could introduce some artificial delay in the nushell startup, but I hate to intentionally slow things down.
","upvoteCount":1,"url":"https://github.com/nushell/nushell/discussions/14021#discussioncomment-10867405"}}}Two-Line Prompt Theme Issue when Using Oh My Posh #14021
-
|
I've encountered an issue with the Two-Line Prompt Theme when using Oh My Posh on Windows. The problem occurs when I execute the following steps:
I get incorrect rendering as follows: When starting: ┏[ hyoryu][ RAM: 28/63GB][ ~]
┖[ 01:52:45] ♥After entering ┏[ hyoryu][ RAM: 28/63GB][ ~]
┏[ hyoryu][ RAM: 28/63GB][ ~]
┖[ 01:53:21] ♥ aThe creator of Oh My Posh cannot reproduce this issue, but I have been able to reproduce it on three different computers(I use GitHub to store the same set of configurations). I have no idea why this happens. Could anyone help me? Details are available at: |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 3 replies
-
|
I said this over at the omp repo too. This is what I think is going on, but I could be wrong. The only time i've seen something like this in nushell is when nushell starts too fast. As I recall, what happens is nushell starts and gets the terminal width, let's say 80x24, in the meantime, your terminal finishes starting and now the terminal width is 100x24, but nushell already knows the size as 80x24, so when you type any character, it realizes it's bigger and redraws the prompt. At least that's my theory. We could introduce some artificial delay in the nushell startup, but I hate to intentionally slow things down. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, I'm using Windows Terminal in maximized mode. I tried changing the window size to default, and the issue disappeared. When I tried using a nearly full window size (190 columns * 50 rows), there was also no problem. Maximizing the window is quite important to me, so I’ll have to put up with this issue. However, I'm grateful to know the possible cause of the problem. Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
After updating Nushell to 0.99.1, this issue also disappeared when maximized. I'm quite certain it's unrelated to oh-my-posh version 24.1.0, as I tested it after updating. I looked through the update notes for Nushell versions 0.99.1 and 0.99.0 and didn’t find any directly related fixes. The changes in 0.99.1 are minor, so I guess the issue might have been resolved in 0.99.0. |
Beta Was this translation helpful? Give feedback.
-
|
you could check fdncred's theory by running i frequently have such issues when using a nested terminal emulator (dvtm, tmux, screen, fterm.nvim, yaft, etc), but those are extremely buggy with any program in any context and get even worse when used via |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your answer. It is indeed related to the terminal window size, but I don’t really want to sacrifice shell performance for a better appearance, so I’ll probably maintain the status quo. As for the second solution, to be honest, I’m not very familiar with shell, so it’s a bit challenging for me. I might try it at some point. Overall, thank you for your response! |
Beta Was this translation helpful? Give feedback.
I said this over at the omp repo too. This is what I think is going on, but I could be wrong.
The only time i've seen something like this in nushell is when nushell starts too fast. As I recall, what happens is nushell starts and gets the terminal width, let's say 80x24, in the meantime, your terminal finishes starting and now the terminal width is 100x24, but nushell already knows the size as 80x24, so when you type any character, it realizes it's bigger and redraws the prompt. At least that's my theory. We could introduce some artificial delay in the nushell startup, but I hate to intentionally slow things down.