[Top][All Lists]

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

Re: moving point over invisible and intangible text

From: Miles Bader
Subject: Re: moving point over invisible and intangible text
Date: Thu, 16 Oct 2003 19:31:56 -0400
User-agent: Mutt/1.3.28i

On Thu, Oct 16, 2003 at 07:06:20PM -0400, Richard Stallman wrote:
> I think move-to-column should probably pay most attention
> to logical lines in the buffer.


If that's the case then it probably shouldn't follow display properties at
all, and should _only_ perform `logically' (call this [X]; I guess this the
current way move-to-columns works), and the documentation should emphasize
the fact that this may not do the right thing if any display properties are
used.  I don't think that simply _preferring_ logical layout, but also
_sometimes_ paying attention to display-only layout, is a very coherent

Also, then a display-specific version (call this [Y]) would be needed,
because in many places, that is the right thing to do (almost any place you
use display properties I think).  I guess this is sort of what
line-move-to-column is doing.

My question is then, are there any places, in practice where (1) you would
prefer `logical' operation (usually when editing a file), but (2) _also_ use
display properties in a way that [Y] could not be used?  IOW, I think that in
practice, you either want [Y] because you care about the display layout in
the presence of display properties, and aren't going to save the changes, or
you simply aren't using display properties at all, in which case [Y]
performs the same as [X] anyway.

Are there counter-examples to this?

o The existentialist, not having a pillow, goes everywhere with the book by
  Sullivan, _I am going to spit on your graves_.

reply via email to

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