Re: Buffer's point changes when frame closed.

ms> What do you mean by "programs"? It seems you mean exactly the ms> same thing as what I meant by "commands" Stephen> No. Commands are programs, but so are hook functions, which need not Stephen> be commands. ms> Currently, there *is* synchronicity in places where the user ms> is not typing, namely in selected windows of non-selected ms> frames. Stephen> I have no idea what that means in terms of the XEmacs I have in front Stephen> of me. If I type into a window on a buffer, then the buffer point is Stephen> synched to that window, and is not the same as the window point in a Stephen> selected window on that buffer in a non-selected frame (except by Stephen> accident, and if I move in the selected frame, it won't be any more). Stephen> At least, not in any XEmacs build I have immediately available to me. Good. However, some places in the code I've stumbled upon during the window-configuration rewrite perform exactly this kind of synchronization. (And I think this is what the original bug report was about, as well.) This means I was probably wrong in thinking there's lots of code depending on that behavior. -- Cheers =8-} Mike Friede, Völkerverständigung und überhaupt blabla