Bugzilla – Full Text Bug Listing
| Summary: | [launching] VM Argument box auto-wraps contents and inserts spaces where wrapping occurs | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Darryl Miles <darryl> |
| Component: | SWT | Assignee: | Bogdan Gheorghe <gheorghe> |
| Status: | CLOSED WONTFIX | QA Contact: | |
| Severity: | major | ||
| Priority: | P3 | CC: | cocoakevin, ericwill, Michael_Rennie |
| Version: | 3.2 | Keywords: | triaged |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | stalebug | ||
|
Description
Darryl Miles
I found a workaround by using Ctrl-Enter to insert newlines this exposes a real space character in my argument string (that I could not see otherwise). I have also found other punctuation character causing linebreaks like slash "/". With the Ctrl-Enter workaround this is more a visual problem than a serious issue, so downgrading report. This also wraps (on the slash characters as well as minus character): -Dfoo=/one/two/three/four/five/size when creating the tab control we are simply creating a standard swt text control with the wrap style bits specified. I am not sure there is anything we can do to control the wrapping behavior, but I do agree this is a very bad problem. sending to swt to for comment. Is there anything we can do to prevent/handle wrapping breaking whole words? You cannot change the way that it wraps, but wrapping should not be inserting spaces for you either. I suspect that this has already been fixed in either Pango or GTK as I cannot reproduce it. Darryl - what versions of Pango and GTK are you running? (rpm -q Pango gtk2) # rpm -q pango gtk2 glib2 pango-1.8.1-2 gtk2-2.6.10-2.fc4.4 glib2-2.6.6-1 Does the GTK API not provide a mechanism to provide your own wrapping delegate and also provide automatic horizontal scrollbar appearance when wrapping makes things too big to fit in the window ? There is some sort of control to plug wrapping mode already in the GTK API, http://developer.gnome.org/doc/API/2.0/gtk/GtkTextView.html#GtkTextView--wrap-mode There is API to insert a "display line" which from glancing at the reference manual is used for inserting lines by the wrapping mode, but not putting anything into the character buffer the text is backed by. gtk_text_view_forward_display_line(); I can not be sure that the insertion of the NewLine was caused by wrapping or with my editing. The Ctrl-Return approach exposed the problem and allowed me to fix. So I downgraded severity. I still think the remaining part of the bug is a problem: * Its difficult to diagnose/see how the wrapping affects VM arguments. * Here is a clear case where a bespoke wrapping mode is needed. Is it possible to have a whitespace character inside a single agument as things stand now ? If I quote around argument do I get the expected result during execution (even if the on screen presentation in the multile-line-edit-box due to unwanted wrapping is not perfect). If so then this bug report just a visual problem. what I meant was that SWT only provides one way to wrap, so from the perspective of the arugments tab of the launch configurations dialog, the choice is use SWT.WRAP, or don't use it. Regardless of how it wraps, GTK/Pango should never be inserting extra spaces into your text. I'm running GTK 2.8.20. I'll try to reproduce this with 2.6. I think the point I was hilighting was that it does not matter if it "does" or "does not" because it is not clear to the user anyway. Can you confirm which native GTK wrapping mode is in use when wrapping mode is enabled, given there are 3 modes of operation. Maybe one of the other modes is better suited. http://developer.gnome.org/doc/API/2.0/gtk/GtkTextTag.html#GtkWrapMode Still reproducible on 4.9, GTK3.22, and Fedora 28. This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. |