Re: flyspell + longlines: hang/wait

[David Reitter]

On 28 Oct 2005, at 04:48, Richard M. Stallman wrote:

> Regarding Python code: what you want makes sense, and could be
> a useful feature.  But it is a completely different feature
> from the one longlines mode is trying to implement.

Right. Maybe we need both. Maybe Kim's patch might do the job?
All we need is a patch that wraps lines (during display) at the  
ultimate whitespace / word boundary
and bind arrow up/down to something more useful than previous/next- 
line. From the last change, even normal editing would profit  
(although that might be arguable - I don't know).
move-to-window-line seems to contain code that does part of the job.

> Regarding LaTeX, I find it incomprehensible that you want to record
> each paragraph as a single long line.  I can't argue with your tastes,
> but I will certainly not make that the recommended way to edit LaTeX
> code in Emacs.  Forget it!

Fair enough, no recommendation needed.
I for my part just don't know how to stay flexible with respect to  
the frame width that I (and my co-authors) like to use.

>     What I am suggesting is that the original representation in the  
> file
>     is respected. No conversion.
>
> That is an interesting idea, and I can see what it would mean in the
> cases you want to use (paragraph = one long line).]  I don't see what
> this would mean, concretely, in the case where you edit a file
> composed of filled paragraphs.  Editing should result once again in
> filled paragraphs.  This means that the number of lines in the
> paragraph has to change as you edit it.  And what you save it, the
> file should contain newlines where you see newlines on the screen.

To distinguish paragraph breaks from newlines (without meaning),  
LaTeX uses double newlines.

For Emacs it would just mean that only hard newlines are saved, but  
not the ones that are purely visual.
There is no change needed in loading or saving buffers.  Do  
everything just like now, just do wrap the lines at whitespace  
positions and change the up/down bindings.

>  "Mixing modes" is a side issue.  I'm talking about using just one  
> mode,
> the mode with no hard newlines inside a paragraph.  That must not be
> one long line in the file.

What was the reason for that again?
Other editors use this without problems.