Subprocess log in Command log

[Its-Just-Nans]

Is is possible to not leave lazygit for a subprocess ?
And show the ouput in the Command log instead

Linked to:

• Skip "press enter to return to lazygit" #1576 (comment)
• Skip "press enter to return to lazygit" #1462

[stefanhaller]

Depends on what kind of subprocess you are talking about: custom commands? calling an editor? making a commit? The answer will be different for all of these.

[Its-Just-Nans]

The classic "git commit" for example which leaves the interfaces and ask "Press enter to return"

[stefanhaller]

In this case, you have gpg signing turned on in your git config. If you do that, lazygit suspends itself to the background to give you a chance to type your gpg (or ssh) passphrase, should you be prompted for that; this wouldn't be possible in the Command log.

If you know you won't be prompted for a passphrase because you use some gpg/ssh agent that provides it automatically, you can set the following lazygit config to avoid suspending:

git:
  overrideGpg: true

[Its-Just-Nans]

Okay, thanks for the explanation. In my case my GPG is prompted in an external window. So I don't need a cli access

[Its-Just-Nans]

In this case, you have gpg signing turned on in your git config. If you do that, lazygit suspends itself to the background to give you a chance to type your gpg (or ssh) passphrase, should you be prompted for that; this wouldn't be possible in the Command log.

If you know you won't be prompted for a passphrase because you use some gpg/ssh agent that provides it automatically, you can set the following lazygit config to avoid suspending:

git:
  overrideGpg: true

So, it turns out that when I do a merge, lazygit is NOT suspending the process.
So, could we have an option to do the same thing for simple commit ?

[stefanhaller]

So, could we have an option to do the same thing for simple commit ?

I don't understand; the overrideGpg: true config is that option. Did you try it?

The fact that merge doesn't suspend when gpg signing is on is a bug, it should do that in the same way as simple commit does.

[Its-Just-Nans]

The fact that merge doesn't suspend when gpg signing is on is a bug, it should do that in the same way as simple commit does.

Oh okay, sorry I wanted to known why the overrideGpg: true was not the default.
Good to known it's a bug and (I guess) we will have the same behavior soon.

Thanks for your help!