Re: C-n and C-a

[Miles Bader]

Juri Linkov <address@hidden> writes:
>>> For the same reason I think we should not set word-mode in
>>> visual-line-mode.
>>
>> This seems bizarre -- AFAICS, like 95% of the goal of visual-line-mode
>> is to make it easy to enable a word-wrapped mode for editing
>> paragraphs-end-in-newline text (i.e., a display-time version of
>> longlines-mode).
>
> The problem is that currently by default C-n/C-p moves by visual lines,
> but C-a/C-e moves by real lines.  `visual-line-mode' is the only way to
> cause C-a/C-e to move by visual lines.  But it forces `word-wrap' to be
> t even in buffers where word-wrap should be nil (where word wrap gives
> sub-optimal results).

If visual-line-mode doesn't turn on word-wrap, then there needs to be a
new mode which is visual-line-mode+word-wrap, because I think that's an
incredibly common case (probably more so than without word-wrap).

If the only use of visual-line-mode without word-wrap is
programmatically (by other modes), then maybe it's enough to just force
word-wrap off in those modes somehow (either by frobbing the variable
itself after turning it on, or by some let-binding around the mode
invocation).

-Miles

-- 
Run away!  Run away!