> SET-WINDOW-POINT DOESN'T SEEM TO ALWAYS WORK. > > What do you mean by "work"? What in fact happens when you call it? > Your description doesn't include that information.
I mean set-window-point doesn't change point and the cusor remains where it was (at the start of the buffer). > The only response I can give is a general one. People often > misunderstand what set-window-point is supposed to do in cases where > one buffer is displayed at times in various windows. Is that what > happened here? I think it may be due to the interaction between the window-manager and Emacs. Odd things happen when there is more than one frame. The display-buffer problem that I posted earlier relates to make-frame where the doc says: doc> This function itself does not make the new frame the selected frame. doc> The previously selected frame remains selected. However, the doc> window system may select the new frame for its own reasons, for doc> instance if the frame appears under the mouse pointer and your doc> setup is for focus to follow the pointer. In my case it selects the frame even though the window manager is configured for click to focus. When using Edebug, I find that it can select a buffer displaying the current code (the mode line goes dark) without selecting the frame, which seems contradictory. These problems are probably to obscure to convey over e-mail. I will try to debug the C code one day. Nick _______________________________________________ Emacs-pretest-bug mailing list [email protected] http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
