Re: [Emacspeak] Problem when editing a document with emacspeak

[Robert Melton <lists@xxxxxxxxxxxxxxxx>]

I almost never have long lines in code, thank goodness.  Sometimes a new
dev needs to be taught the importance of short lines, but that doesn't take 
long. Have had the 80 vs 100 vs 120 vs .. blah blah blah conversations 
more times than I would prefer. 

Markdown files I routinely find with very long lines, full paragraphs that are
on a single line, sometimes I just want to fix a part that is wrong without 
having a massive diff of me fixing the formatting of it all. I think there is a 
markdown auto formatter out there that seems to encourage this. 

> On Jan 22, 2024, at 10:47, T.V Raman <raman@xxxxxxxxxx> wrote:
> 
> I personally dont think highly of visual-line mode; it's a concession
> to the binary-file format leaning world which first sucks you in with
> long lines. It also leads to poor code quality because unless line
> length is enforced, the codebase eventually degrades to a mess of
> long, unmanageable lines. So by all means invest time in improving it,
> but if you submit patches to  Emacspeak in general, I'll ruthlessly
> reject any patch that creates lines longer than 80 columns. See make
> target ll in lisp/makefile 
> --