Info-scroll-up/down are bound on the mode-line (over the node name) to
mouse-1 and mouse-3. However, in a split window configuaration with Info at
the top and the bottom window selected, clicking there scrolls the _bottom_
window, and Emacs gets confused if this is already at the top or bottom.
See how mouse-drag-mode-line-1 handles this:
(defun mouse-drag-mode-line-1 (start-event mode-line-p)
"Change the height of a window by dragging on the mode or header line.
START-EVENT is the starting mouse-event of the drag action.
MODE-LINE-P non-nil means dragging a mode line; nil means a header line."
;; Give temporary modes such as isearch a chance to turn off.
(run-hooks 'mouse-leave-buffer-hook)
(let* ((done nil)
(echo-keystrokes 0)
(start (event-start start-event))
(start-event-window (posn-window start))
(start-event-frame (window-frame start-event-window))
(start-nwindows (count-windows t))
(minibuffer (frame-parameter nil 'minibuffer))
should-enlarge-minibuffer event mouse y top bot edges wconfig
growth)
Then it does everything on start-event-window.
Can you implement the same method in Info-scroll-up and
Info-scroll-down?
_______________________________________________
emacs-pretest-bug mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/emacs-pretest-bug
