Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

commit moves to cli with prompt to return to lazygit instead of lazygit tui #4027

Open
WorldTeacher opened this issue Nov 2, 2024 · 5 comments
Labels
bug Something isn't working

Comments

@WorldTeacher
Copy link

I noticed that when i commit a file using lazygit, that after adding the commit message I get redirected to this:
image
instead of the usual lazygit ui. Is this intended or was this changed and I just did not notice?

To Reproduce
open repo
select file(s) to commit with spacebar
add commit message using c
press enter

see the redirect to the terminal

Expected behavior
I get redirected to the normal tui

Screenshots
see screenshot above

Version info:
commit=095eb130e, build date=20241102.214908, build source=unknown, version=v0.44.1.095eb130e, os=linux, arch=amd64, git version=2.47.0
(same issue appears in current aur package)

@WorldTeacher WorldTeacher added the bug Something isn't working label Nov 2, 2024
@waelmahrous
Copy link

Hmm I can't seem to reproduce this issue. Goes back to the Lazygit UI for me.

@WorldTeacher
Copy link
Author

Is there anything I could to to somehow log my actions / lazygit's responses?

@waelmahrous
Copy link

waelmahrous commented Nov 5, 2024

Yes, this is copied from the readme:

Run lazygit --debug in one terminal tab and lazygit --logs in another to view the program and its log output side by side

Maybe check those logs for any pointers, or upload a copy of them here so you can get more accurate assistance. Hope this helps :)

@WorldTeacher
Copy link
Author

sorry for not replying sooner, got sick and could not really focus on stuff.

lazygit --debug exits as soon as I confirm the command

This is a log that shows what happens:
lg_logs.log

@waelmahrous
Copy link

Ah yeah that's another issue seen in #4002. Try downgrading to Go 1.22 and retrying the debug logs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants