GNU bug report logs - #3438
emacs 23.0.9{,3,4} dired mode bug(?)

Previous Next

Full log

View this message in rfc822 format

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: "Drew Adams" <drew.adams <at> oracle.com>
Cc: "'Chong Yidong'" <cyd <at> stupidchicken.com>,
        "'T.V. Raman'" <tv.raman.tv <at> gmail.com>, <ams <at> gnu.org>, <eliz <at> gnu.org>,
        <stephen <at> xemacs.org>,
        "'Andrew W. Nosenko'" <andrew.w.nosenko <at> gmail.com>,
        <emacs-devel <at> gnu.org>, "'ishikawa'" <chiaki.ishikawa <at> ubin.jp>,
        <3438 <at> debbugs.gnu.org>
Subject: bug#3438: please make line-move-visual nil
Date: Mon, 01 Jun 2009 16:11:49 -0400

> More typically (in formatted buffers), we want to reflect the use of newlines
> (they are positioned intentionally) and maintain the current column for line
> movement, but there is no single, privileged column (e.g. file name) that we
> want to constrain point to, as there is in Dired.

I don't know if it's typical, but for most of those kinds of buffers you
describe as "formatted", I think they should at least set truncate-lines.

> Each formatted buffer could individually define its own line-movement
> commands, which amounts to just binding `line-move-visual' to nil
> around a call to `next-line'.  But that would be a bit silly.
> Better to just let the variable be buffer-local.  And provide nil as
> the default value for most formatted buffers.

Any major mode is free to (set (make-local-variable 'line-move-visual) nil).
As of now, I don't think any mode bothers to do that.

> BTW, you didn't answer the questions about the poll.
> How's it coming along?  Where is it?

I can't think of any poll which would bring any satisfactory answer to
the discussion.


        Stefan

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.