view BUGS @ 103174:27ea4d4a56a4

(split-window-sensibly): New function. (split-height-threshold, split-width-threshold): State in doc-string that these affect split-window-sensibly. Change customization subtype from number to integer. (window--splittable-p): Rename to window-splittable-p since it's referred to in doc-string of split-window-sensibly. Update doc-string. (window--try-to-split-window): Unconditionally call split-window-preferred-function and move splitting functionality to split-window-sensibly (Bug#3142). (split-window-preferred-function): Rewrite doc-string. Don't allow nil as customization type.
author Martin Rudalics <rudalics@gmx.at>
date Thu, 07 May 2009 09:21:23 +0000
parents fb8bf24d2eb9
children ac52af4a044c
line wrap: on
line source

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,"

Please first check the file etc/PROBLEMS (e.g. with C-h C-p in Emacs) to
make sure it isn't a known issue.