I also have this issue. I've noticed that not every multi-line commit message will cause this behavior.
This bug only occurs for me (v0.0.6) if the first line of the comment is followed immediately by another line instead of a blank line. For example: Let's say that this line you are reading is the start of a commit message/comment... This line, occurring directly after the previous line with no additional empty line triggers the bug. However, if this line is the start of a commit message/comment... This line, separated by the first line by an empty line, will not trigger the bug. I realize that it is common convention in GIT commit messages to use a blank line to separate the "brief" description from the longer detailed comments; However, since gitg only uses a single line of text in the "subject" column to provide a "brief" description, the text within the "subject" field should end at the first end of line symbol (either '\012' or '\015' -- carriage return or line feed ). Additionally, since the commit message/comments are displayed in a scrollable region, long line lengths should have no effect on the window size whatsoever... I would open a new bug for the too much text in the "subject" field, but I'm pretty sure that it is directly related to the window being overly resized. Kind regards, Tim -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/636314 Title: gitg set extreme window size on long commit comment -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
