On Thu, May 18, 2023 at 08:49:26AM -0700, Randy Dunlap wrote: > On 5/18/23 08:01, Luis Chamberlain wrote: > > * use 80 char length as if we're in the 1980's > > Well, like Jon said, long lines are difficult to read, even on printed paper. > That's (at least one reason) why newspapers(!) have narrow columns of print. Makes sense! > Anyway, thanks for doing it. Heh yeah, I just trying to follow the convention, but I didn't know it was a special-case for bumping up to 100 only, and that it was definitely not good for docs. It's easy to loose it though, we have one for commit log, one for length on code with an exception, and we have a clear perference for docs. Makes me wonder if editors pick up on project specific requirements somehow? So for instance I used to have incorrectly; set textwidth=100 autocmd FileType gitcommit set textwidth=72 set colorcolumn=+1 Cleary that 100 is wrong now and I've now updated it bacak to 80. Could one be used for FileType for rst and ascii files? If we shared something on the top level which lets developers optionally pick up on project specific guideline it would be a less common problem to ping back / forth about this. Curious how many patches "length" is the reason introduces a latency for patches getting upstream. You figured this would be a simple fix in year 2023 :P Thanks for the fix recommendations! I'll wait and see if others find others! Luis
