powerlevel10k | March 2019 after a week-long discussion | Command Line Interface library

git is using the pager (usually less command) for its output.

you can configure it via core.pager for all the git commands or use per command config pager.; there is also GIT_PAGER env variable

the easiest way to skip the paging for one time is to use --no-pager option for command; and to disable the paging completely git documentation suggests:

To disable pagination for all commands, set core.pager or GIT_PAGER to cat.

git config --global core.pager cat

you may experiment with setting the pager to less -F -X; this will make less page the content only if it does not fit the screen -F, and not to clean the terminal buffer -X

git config --global core.pager 'less -F -X'

or simply disable the pager for the branch command

git config --global pager.branch false

Try first to clone again your repository in a separate, to check if the issue persists (if the zsh prompt, in that new folder, is still incorrect).

From issue 559, you can see what produces the yellow segement:

You have a small extension (possibly part of the powerlevel10k theme) that colorizes the text on the command line. One thing it does is do progressive path lookup on the name of the command you are typing. If no command is found, the text is red. Once a valid command is found, the color becomes green.

This is independent of whether the command, when executed, succeeds or fails. test with no arguments fails, as noted by the 1x in the following prompt.

It's not a feature of P10k. Just put this in your .zshrc file, before initializing the prompt:

Something you do in .zshrc following source ~/.fzf.zsh breaks it. Make sure ~/.fzf.zsh occurs after that, most easily accomplished by moving it to the end of the file.

I was facing a similar issue. I was able to apply the workaround and later on, Jupyter notebook worked as expected.

Alternatively, you can check the path variables as well.

Try removing the npx plugin from plugins=(...) in .zshrc. I had the same problem and that solved it for me.

When running in a regular terminal, unless you capture or redirect git's output with $(git ...) or git ... | otherprogram, isatty(1) is true, so git automatically invokes a pager to let users read content too long to fit on one screen.

1. See if the problem goes away without a pager.

   • Does git --no-pager branch still have issues?

2. Check which pager is in use.

   • declare -p GIT_PAGER will show a pager configured only for git via the environment.
   • git config core.pager will show a pager configured only for git via its config files.
   • declare -p PAGER will show a pager configured to be used by your OS in general.

3. Check how that pager is configured, and try clearing or simplifying that configuration.

   • If your pager is LESS, declare -p LESS will show options configured for it via the environment, and unset LESS will temporarily clear those options.
   • If your pager is MORE, declare -p MORE will show options configured for it via the environment, and unset MORE will temporarily clear those options.
   • For another pager, consider reading its manual.

The OP had LESS='-F -g -i -M -R -S -z-4' exported in their environment. The -F argument to less instructs it to exit if there's less than one page of content to be displayed.

On the OP's (MacOS) system, the stock version of less, when called with -F, exited before emitting the original content to stdout; this could be repaired either by removing that flag, or by installing a newer version of less.

So I found the answer. It wasn't about bash or zsh, and so that's why I wasn't finding a solution.

The issue was with the AWS command as it was running the inserts using AWS CLI. The CLI has a field AWS_PAGER which I'm assuming has a default setting of AWS_PAGER = "less".

Whether it's default or not, adding export AWS_PAGER="" fixed the issue.