zthxxx/jovial

Tabbing collapses previous lines

royemosby opened this issue · 13 comments

When tab is hit while using this theme, it moves the command line up, removing the lines above it. If this is intentional, how is it disabled?
tab-collaps

@royemosby thanks for use and feedback, what’s the version you used now?

Run echo ${JOVIAL_VERSION} can see it

2.0.0

@royemosby This bug should be fixed in the newer version, current is v2.3.0, could you upgrade and try again?

Changelogs see: https://github.com/zthxxx/jovial/blob/master/CHANGELOG.md

Upgrade guide see: https://github.com/zthxxx/jovial#upgrade

@zthxxx after running curl -sSL https://github.com/zthxxx/jovial/raw/master/installer.sh | sudo -E bash -s $USER it only takes me up to 2.0.2
Screen Shot 2021-12-30 at 8 38 35 AM
.

@royemosby did you restart your terminal to reload zsh? Due to the command only download files but not reload (maybe I need add to docs...)

I started a new session after completion. Even after restarting iTerm, i'm still only @ 2.0.2.

@royemosby That's weird. I tried back to 2.0.0 just now and run install command again, It exactly did upgrade to 2.3.0.

Maybe network cache? I need more info for troubleshooting...

Additionally, for upgrade, you can copy(download) the theme file (jovial.zsh-theme) to override your local theme file ~/.oh-my-zsh/custom/themes/jovial.zsh-theme (that's also what the install command does)

I was thinking about manually copying the theme but didn't know if it'll break anything. With you saying that, I'll go ahead and do that. Thanks for the assistance!

(that's also what the install command does)

Curious that did not work for me then. The move to 2.3.0 fixes my original problem.

I'm glad I solved your problem.

And would you run the curl commands below and take screenshot to me? (for troubleshooting in network)

curl -sSL https://github.com/zthxxx/jovial/raw/master/jovial.zsh-theme | head

curl -sSL -H 'Cache-Control: no-cache' https://github.com/zthxxx/jovial/raw/master/jovial.zsh-theme | head

Thanks, that looks right.

The upgrade-version issue maybe some other reason, but not about this issue with original problem, so I closed.