WARNING terminal is not fully functional, but sometimes it is?

[zamlz]

Describe the bug
Here is a picture of the issue.

As you can see, the subwindow is showing the error message

WARNING: terminal is not fully functional

However, if I press ENTER on the file in my FILES view, I am able to view and interact with my changes as expected.

To Reproduce

1. Open up LazyGit
2. Press enter on a file to change the view of the second window
3. See that it is working
4. Press escape and leave that view to see it being broken again.

Expected behavior
It shows the correct window

Version info:

commit=, build date=, build source=nix, version=0.42.0, os=linux, arch=amd64, git version=2.45.1

git version 2.45.1

[olexii-lysenko]

I have the same issue. I'm using lazygit in my neovim inside the tmux (zsh, macOS Sonoma 14.5). Was trying to handle this by changing my .zshrc:
if [ -n "$TMUX" ]; then
export TERM="tmux-256color"
else
export TERM="xterm-256color"
fi

and my .tmux.conf:
set -g default-terminal "tmux-256color"
set-option -ga terminal-overrides ",xterm-256color:Tc"

and explicitly set there the colors (as a GPT-proposal), but end up with no results.

[iamrx0]

Having the same issue :( Any progress ?

[zamlz]

No progress on my end. The terminal I'm using is alacritty

> echo $TERM
alacritty

I tried temporarily overriding the TERM variable with the following terminal names and that didn't change behaviour either. Used, xterm, xterm-256color and tmux-256color 😭

[Woit]

any updates?

[zamlz]

I haven't had a chance to test anything more on my end unfortunately :(

…

On Friday, July 12th, 2024 at 2:15 AM, Egor M ***@***.***> wrote: any updates? — Reply to this email directly, [view it on GitHub](#3704 (comment)), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/ACSAQS7T4QVUXKJXYVNHFE3ZL6NDVAVCNFSM6AAAAABKDX2L6CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMRVGE3DINZWG4). You are receiving this because you authored the thread.Message ID: ***@***.***>

[Djedouas]

Same with 0.43.1 here

[Gabriel-Rockson]

Run into this on xterm-kitty.

[minseon9]

@zamlz
In my case, it was due to lazygit configuration located at Library/Application\ Support/lazygit/config.yml(location differ on other OS).

gui:
  showIcons: true # DEPRECATED
git:
  paging:
    useConfig: true

I just delete all configuration, and problem is solved.

[Lonzoghf]

In my case, I delete "useConfig" option located at Library/Application\ Support/lazygit/config.yml(location differ on other OS).

before:

gui:
 showIcons: true # DEPRECATED
git:
 paging:
   pager: delta --dark --paging=never
   useConfig: true

after:

gui:
 showIcons: true # DEPRECATED
git:
 paging:
   pager: delta --dark --paging=never

I just delete useConfig:true, and it worked.

[Djedouas]

For me it was the pager: "less" config option I had that was creating the error.

Leaving pager empty with pager: "" fixes the problem.

[iamrx0]

In my case, I delete "useConfig" option located at Library/Application\ Support/lazygit/config.yml(location differ on other OS).

before:

gui:
 showIcons: true # DEPRECATED
git:
 paging:
   pager: delta --dark --paging=never
   useConfig: true

after:

gui:
 showIcons: true # DEPRECATED
git:
 paging:
   pager: delta --dark --paging=never

I just delete useConfig:true, and it worked.

Same for me.

[zamlz]

Oh wow, y'all are right. I had the useConfig: true set on mine and I removed it and everything is working again. I wonder why I set that in the first place though?

[zamlz]

Okay I must have removed whatever pager I had set in .gitconfig
The documentation here actually is key.
https://github.com/jesseduffield/lazygit/blob/master/docs/Custom_Pagers.md#using-git-config

I did not realize it would still try to use less even if nothing was set on the .gitconfig side.