view BUGS @ 30362:fc017b1b2a7d

(foreach_window): Instead of a fake variable argument list, take one USER_DATA argument. (foreach_window_1): Likewise, and call callback functions with two args, the window and USER_DATA. (struct check_window_data): New struct. (check_window_containing): Use it. (window_from_coordinates): Set up a struct check_window_data for foreach_window. (add_window_to_list, freeze_window_start): Change parameters according to new calling convention.

If you think you may have found a bug in GNU Emacs, please
read the Bugs section of the Emacs manual for advice on
(1) how to tell when to report a bug, and
(2) how to write a useful bug report and what information
it needs to have.

There are three ways to read the Bugs section.

(1) In a printed copy of the Emacs manual.
You can order one from the Free Software Foundation;
see the file etc/ORDERS.  But if you don't have a copy on
hand and you think you have found a bug, you shouldn't wait
to get a printed manual; you should read the section right away
as described below.

(2) With Info.  Start Emacs, do C-h i to enter Info,
then m Emacs RET to get to the Emacs manual, then m Bugs RET
to get to the section on bugs.  Or use standalone Info in
a like manner.  (Standalone Info is part of the Texinfo distribution,
not part of the Emacs distribution.)

(3) By hand.  Do
    cat info/emacs* | more "+/^File: emacs,  Node: Bugs,"