Re: need option so line-move-to-column ignores fields, plus patch

[Richard Stallman]

    >     > | 1. With the cursor adjacent to the right of any bar,
    >     >  |   if you move forwards a line (^N), the cursor slips to column 0.
    >
    >     I don't see where else the cursor can possibly go in #1.
    >
    > It can go to after the bar.  That's where it should go.

    This logic is wrong.  Consider the case where there is a field' in the
    region denoted XXXXXX; everywhere else, the `field' property is null.
    Point is initially located at the position indicated by `|'.

      |
    XXXXXXXXX

    Clearly, pressing C-n should move point to the start of the field.

I don't see why that would be right.  Moving to the end of the field
seems just as plausible to me.  But it might depend on the intended
semantics of the field.

    > I think we need a concept of temporary goal fields to go with the
    > temporary goal column.  When you type the first line-move command
    > it should record some info about the field you're in when you start.
    > Then if a field with the same property appears on the line you move to,
    > it should be handled as if it were -- in some sense -- "the same".

    This is a feature, not a bug.

Does C-n do the right thing in the modes that use fields?
If not, then I think this is a bug fix.  If so, maybe this is
a new feature.

    But if this behavior (i.e., treating non-contiguous fields as
    identical for the purpose of line-motion) is really the behavior you
    want, and we agree that it will close this bug, I can implement this
    even more simply than that, by comparing `field' properties at the
    relevant places inside line-move-finish.

Please give it a try.