GNOME Bugzilla – Bug 591364
Certain characters do not wrap.
Last modified: 2010-04-19 01:09:44 UTC
Please describe the problem: When certain characters ([, ], (, ), {, }, ;, :, ,, ., !, ?, ¡, ¿, /, ' ' (space) and — (em dash)) are repeated enough times to evoke a line break, the GtkTextView does not wrap them. Although this functionality is beneficial in sane environments where the above characters are not expected to be repeated more than three times, applications that use GtkTextView in an environment where wrapping is preferred (Pidgin, IRC clients, etc.) have their windows either stretched—occasionally beyond the size of the screen—or a horizontal scrollbar appears, which then requires the user to scroll to read text. Steps to reproduce: 1. Open up gedit, Pidgin or any other application that uses a GtkTextView for input. 2. Hold down the '[' key in the widget. Actual results: Rather than breaking the line, the GtkTextView expands horizontally. Expected results: When used in a typographical context, [](){};:,.!?¡¿/ — should be affected by wrapping the way regular characters are. Does this happen every time? Yes. Other information: The following is a PyGTK example that creates a window with a GtkTextView embedded in it to demonstrate. #!/usr/bin/python import gtk window = gtk.Window() window.set_default_size(80, 60) window.connect('destroy', gtk.main_quit) window.add(gtk.TextView()) window.child.set_wrap_mode(gtk.WRAP_CHAR) window.show_all() gtk.main()
this bug affects me too
I am also seeing this issue, was trying to use the textview to log data from a background task, which is not very useful without wrapping since the BG task runs scripts which output a lot of periods. To work around this I either have to modify a large number of scripts to stop outputting periods, or allow the text view to have a scrollbar. Neither are desirable workarounds. My environment is Ubuntu 8.10, Ruby/GTK bindings - would be willing to help someone collect debugging data / etc, this bug is definitely worth fixing.
*** This bug has been marked as a duplicate of bug 131625 ***