[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: please make line-move-visual nil

From: Drew Adams
Subject: RE: please make line-move-visual nil
Date: Mon, 1 Jun 2009 16:18:55 -0700

> > In Dired, <up> and <down> call dired-previous-line and 
> > dired-next-line, which should not be affected by line-move-visual.

Yes, but imagine if Dired _did_ use `next-line' for <down> or `n', so it was
thus affected.

Try it: M-x local-set-key n next-line. Narrow the Dired window so file names
wrap. Try `n' with point at various horizontal positions.

Do you really think `line-move-visual' is a good fit here? No? No, and the same
is true for other buffers where newline chars and line length matter.

In buffers where a line (line of code, line of Dired, etc.) is defined by ending
in a newline, moving to the next line does not mean moving to the wrapped part
of the same line.

If `truncate-lines' is helpful in this respect (you don't even see the wrap),
then so is nil `line-move-visual' (you don't move to the wrap, even if you see

reply via email to

[Prev in Thread] Current Thread [Next in Thread]