> I have to say I find it simple and consistent, line breaking always behaves > the same, it breaks **at** the specified column, always, no matter what, > thats being consistent.
It is not doing it consistently but not correctly. Regardless of whether you take 72 to mean column 72 (73rd column starting at 0) or 72 characters (ending inclusively with 71 starting at 0), that is not what the program is doing. It is reflowing but only allowing 71 characters per line, and the same occurs with Line Breaking. There is no possible way to interpret The setting "Column: 72" in the Preferences, Editor, Display tab as 71, unless it is a bug and interpreting column 72 as exclusive, and even in that case the right side of the character is still touching it not going past it. It would be reasonable for any user to assume that since it places the green line after 71 that it is starting at 0, or that it means 72 characters is a "long" line. Either way, that is where the green line is and not how reflow and Line Breaking behave. I confirmed it is not a problem with the pixel-based approach of Scintilla discussed here (may not apply to recent versions): https://lists.geany.org/pipermail/users/2012-March/007951.html because the behavior is the same whether I write a `t`, `m`, or `.` for the last character of "not" in the example below, Geany only allows 71 characters per line for Line Breaking or reflow. I can't type up to the green line with line breaking on, and with it off, I can't reflow up to it. My long line marker is 72 (and always has been so the problem is not something like #1358). Example: ``` Hippopotamuses may like apples but we will never know because I will not get that close. ``` (Geany doesn't allow "not" on the same line. Though that would be 72 characters, Geany only allows 71) I am using Geany 1.38. -- Reply to this email directly or view it on GitHub: https://github.com/geany/geany/issues/2078#issuecomment-1722302014 You are receiving this because you are subscribed to this thread. Message ID: <geany/geany/issues/2078/[email protected]>
