After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 637880 - Selecting a commit with a long message expands window out of screen.
Selecting a commit with a long message expands window out of screen.
Status: RESOLVED DUPLICATE of bug 636529
Product: gitg
Classification: Applications
Component: gitg-0.x
git master
Other Linux
: Normal major
: ---
Assigned To: gitg-maint
gitg-maint
Depends on:
Blocks:
 
 
Reported: 2010-12-23 15:31 UTC by Nicolas Bigaouette
Modified: 2013-06-13 13:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Patch that ellipsizes the subject (407 bytes, patch)
2011-09-19 14:41 UTC, David Fraser
none Details | Review

Description Nicolas Bigaouette 2010-12-23 15:31:10 UTC
A collegue of mine has the bad habit of commiting with huge messages on a single line (no word wrap).

When I select such commit in gitg's history, the gitg window expand so gitg's "Subject" field is all visible, making the bigger then the screen.

To get back to normal, I have to select a commit with a decent message length and use my window manager to maximize gitg's window.

Using gitg 0.0.6 on ArchLinux x86_64 (KDE).

Thanks!
Comment 1 David Fraser 2011-09-19 14:41:19 UTC
Created attachment 196949 [details] [review]
Patch that ellipsizes the subject

The subject is not ellipsized by default, whereas the Parent subject is; the attached patch simply does the same for the main subject. Since the full subject is viewable inline, it seems a reasonable compromise
Comment 2 David Fraser 2011-09-19 14:43:01 UTC
See also #636529
Comment 3 Jean-Philippe Fleury 2011-11-04 18:47:11 UTC
I think this report can be closed as a duplicate of bug 636529
Comment 4 Sindhu S 2013-06-13 13:53:50 UTC
Moving bug to gitg-0.x

*** This bug has been marked as a duplicate of bug 636529 ***