Pratyush Yadav

> I don't see any way to close the stdin to the hook process, so it's impossible to commit using the GUI as-is. I've "solved" this by just adding calls...

@MOZGIII FYI, you can take a look at [this](https://lore.kernel.org/git/[email protected]/) discussion to find out more ways to set the theme that does not involve editing the git-gui source. Anyway, I think...

Hi @tasty0tomato, As of now I don't make releases for Git Gui. Part of the reason is that I just have not bothered to do so, but part of the...

@PhilipOakley ok, makes sense. I will start updating the version string from now on. As for what it will look like, I don't think using Git's version makes a lot...

Cc @last-partizan @rdiez @MaxLap git-gui recently got better theming support. The background colors are the ones from the default Tk theme. Unfortunately it looks like the defaults are not very...

>I tried using your 2nd point and it seemed to have no effect, or barely any effect, and not on those colors. Huh... That should _not_ happen and is certainly...

Hi @JessIAm, Yes, git-gui does not have very good documentation. The point has been raised before but I, or someone else, have not been able to get any meaningful progress...

Yes, we do use `xdg-open` for opening files. Allowing opening files with a custom editor command shouldn't be too difficult. I will look into it when I can find some...

I agree with Bert. The kind of autocompletion you linked to is just way too much to be a part of a relatively simple frontend for Git. Giving suggestions like...

I'm not sure whether doing half-baked autocomplete is better than no autocomplete. But I guess I should wait till someone comes up with a sample implementation to judge.