Re: line-move-visual never set to nil?

["Lennart Borgman (gmail)" <lennart.borgman@gmail.com>]

Miles Bader wrote:
> "Lennart Borgman (gmail)" <lennart.borgman@gmail.com> writes:
>>> Macros do not -- and cannot -- make any guarantees about what happens if
>>> you execute them in a different environment, or on different text, than
>>> where they were recorded.
>> Do you mean that there is something that prevents us from temporary
>> turning things off during keyboard macro recording and execution? In
>> that case: what?
> 
> The point is that it doesn't actually help -- there are a million other
> cases that can trip up the user, and the only general solution is for
> users to be aware of problems that can crop up during macro replying and
> be fairly conservative in how they make macros.

I think this case is special. The special thing is the relation between 
the visual move and the buffer point. That relation changes according to 
something that is rather unrelated with the buffer contents but can 
easily be changed by the user. That makes the relation very volatile.

> Having commands work _differently_ during macro recording is guaranteed
> to confuse people, and doing so will probably cause as many problems as
> it "solves".
> 
> -Miles
>