Hi, @alan-kilborn, @coises and All, From the scintilla description, below : SCI_LINESSPLIT(pixels pixelWidth) Split a range of lines indicated by the target into lines that are at most pixelWidth wide. Splitting occurs on word boundaries wherever possible in a similar manner to line wrapping. When pixelWidth is 0 then the width of the window is used. I made a try putting ONLY the 0 value ( instead of 78 ) In Settings > Preferences... > Margins/Border/Edge > Vertical Edge Settings. Well, it happens that for any value ≥ 2, the spliting occurs after 2 characters I also tested with, for example, the value 220, which was larger than my physical screen. However, even in this case, the spliting occurs after 220 chars and not at the window’s width ! Of course, for these additional tests, line-endings were not enabled ! Oh, my God : I forgot to test with the Settings > Preferences... > Margins/Border/Edge > Vertical Edge Settings window completely empty ! Well, in this specific case, the spliting does occur at the window’s width and takes in account the possible increase or decrease in the ZOOM factor ! BR guy038

Tabs v spaces As Peter said, the most important part is consistency. Mixing tabs and spaces together makes no one happy. I will throw out a couple arguments for tabs here: Indentation of code, markup language, et. cetera is meant to show the structure of whatever. Tabs are a logical, structural element. Spaces are physical. Different users may want different sizes of indentation. If i want 4 character indentation and my coworker wants 2, tabs can be set to show our preferred width. Seems for the most part that spaces are winning out though.